Spotfire

Exporting Data
* When exporting data, use a method that is not deprecated by Pandas 1.5.0. (28)
* Better handle exporting nullable column dtypes like `Float64`. (25)
* Add support for exporting GeoPandas `GeoDataFrames` with `MultiLineString` geometry as 'PolyLines' to Spotfire. (19)

Creating SPK Packages
* Use a better parser for requirements as provided by `setuptools`/`pkg_resources`. (4)
* Allow both analyst and server SPK information to be stored in the requirements file brand. (5)

* Support the code signing of built SPK packages with certificates in Windows system certificate stores. (58)

Note that this release is relative to v1.8.3. (https://github.com/spotfiresoftware/spotfire-python/compare/v1.8.3...v1.8.4)

* Reduce the logging of table and column metadata to the data function flow's debug logs to avoid overly-large log output. (48)
* When exporting data, use a method that is not deprecated by Pandas 1.5.0. (28)

Note that this release is relative to `v1.8.2`. (https://github.com/spotfiresoftware/spotfire-python/compare/v1.8.2...v1.8.3)

* Promote `Integer` typed columns to `LongInteger` if they will not fit in 32 bits. Partially restores behavior seen before adding type information for 6 when Python `int`s always exported as `LongInteger`.
* When running data functions, make sure exceptions with causes (i.e., nested exceptions) output the causes in addition to the main exception.

* Fix geopandas problems with CRS objects (geopandas 0.11.0 changed behavior of the 'crs' attribute of GeoDataFrames). (26)
* Expose Spotfire type information on import, and use that information on export. (6)
* Instead of capturing pip output when installing packages for an SPK package, use 'pip list' on the directory the packages were installed to. Fixes problems on systems that do not have a UTF-8 compatible default encoding.

* Tighten up the way we are detecting duplicate packages to remove when building a packages SPK. (24)