New Features
- Add `strict_mode` support to `VersionedAPISession`. Strict mode is now the default, implying API requests will fail if type/version is expected and the response doesn't include it.
- Add `version_strict_mode` config option to `DWaveAPIClient`. It corresponds to underlying session's (`VersionedAPISession`) `strict_mode`.
- Add `VersionedAPISession`, a `requests.Session` subclass (more precisely, further specialized `LoggingSession`) that enforces conformance of API response version with supported version range(s).
- Add `accepts` decorator for declaring accepted media type and response format version (range) on `dwave.cloud.api.Resource` methods.
- Simplify `dwave.cloud.api.resource.accepts` interface (require only `media_type` and `version`), but retain flexibility (pass all keyword arguments to `VersionedAPISession.set_accept`).
- Support `strict_mode` control of API response type validation via `accepts` interface.
Upgrade Notes
- Response type version is now always required (regardless of `strict_mode`) if type is expected and received, and version is expected.
- Enforce D-Wave API response format version on all `cloud.api` resources.
Bug Fixes
- Fix `dwave.cloud.api.resources.accepts` to allow for partial decoration of `Resource` methods. See [\544](https://github.com/dwavesystems/dwave-cloud-client/issues/544).