Eodms-api-client

What's Changed
* janitorial stuff by m9brady in https://github.com/m9brady/eodms-api-client/pull/11


**Full Changelog**: https://github.com/m9brady/eodms-api-client/compare/v1.2.11...v1.2.12

Changes:

- New filter option: `spatial_resolution`: https://github.com/m9brady/eodms-api-client/pull/10#issue-2064225063

**Full Changelog**: https://github.com/m9brady/eodms-api-client/compare/v1.2.10...v1.2.11

Changes:

- Allow users to supply Point and Line geometries instead of limit to Polygon for queries
- Add short example of downloading imagery using an Order ID to README (thanks to user suggestion)
- Switch documentation hosting to GitHub Pages

**Full Changelog**: https://github.com/m9brady/eodms-api-client/compare/v1.2.9...v1.2.10

Bugfix the bugfix

**_Bug introduced in v1.2.7 and included check was insufficient in v1.2.8 so skipping ahead to v1.2.9_**

- recently, the download URL and manifest key in API json responses were not matching, so a check was added that overwrites the download URL with the correct text if a mismatch occurs. Once the API is fixed this check should just by bypassed.
- reported by email from user (thank you)
- begin using content-type header instead of content-length when identifying granules listed as AVAILABLE_FOR_DOWNLOAD but pruned from the order cart
- slight adjustment to CLI usage where the output directory does not need to exist beforehand (client will create it if necessary)

Full Changelog: https://github.com/m9brady/eodms-api-client/compare/v1.2.6...v1.2.9

Adding remote file-size checks when downloading orders

- For some orders, EODMS reports the data as "available-to-download" but when the download links are accessed, nothing is there
- Reported in 8
- To account for these cases, a new check and associated log-message was added to inform the user
- Also added a check for when the EODMS API is down but still returns HTTP-200

**Full Changelog**: https://github.com/m9brady/eodms-api-client/compare/v1.2.5...v1.2.6

Bugfix for National Air Photo Library (NAPL)

- in response to user report 7
- NAPL metadata was not being parsed properly, causing errors
- Fixed the problem and added [some more metadata](https://github.com/m9brady/eodms-api-client/blob/18cebbb87ad31d3d148d66b55da6a97264f40dac/eodms_api_client/params.py#L254-L260) to the result dataframe just for fun

**Full Changelog**: https://github.com/m9brady/eodms-api-client/compare/v1.2.4...v1.2.5