Oaaclient

* New functions in `OAAClient` for managing Veza Queries and Reports. See function doc strings for usage.
* `get_queries`
* `get_query_by_id`
* `create_query`
* `delete_query`
* `get_reports`
* `get_report_by_id`
* `create_report`
* `update_report`
* `add_query_report`
* `delete_report`
* New `utils` method `build_report` to populate a Veza Report and Quires from a dictionary containing the report and query definitions. See function docstring for more details.
* Package provides new CLI command `oaaclient-report-builder` to load a report file directory from JSON file from the command line.

* Added `__str__` and `__repr__` functions to the template classes to help with debugging and simplify printing log/status messages as needed.
* IdP now supports nested groups. A group can be added to a parent group by using the `CustomIdPGroup.add_groups()` function.

* Automatic API retries for connection errors
* New exceptions `OAAResponseError`, `OAAConnectionError` that extend the base exception `OAAClientError`
* `OAAResponseError` raised for API calls that result in an error being returned from Veza
* `OAAConnectionError` raised for API calls that can't complete (for network and other connection errors)
* Use new paging and filtering in Veza APIs to improve performance
* `api_get` automatically processes paginated responses to get all entities. Will return a list of entities or a single value based on API response
* `api_post` will automatically unwrap API response and result `result` or `results` value from API response.
* Provider and Data Source names are now checked for invalid characters in create functions before API call.

* `CustomIdPProvider.users` and `CustomerIdPProvider.groups` dictionaries are now keyed by user/group identity (if provided) to prevent duplicate name collisions. To reference a user or group from the map after creation, use the "identity" value. If an identity is not provided, "name" is used for both identity and key.

* Added support for resource unique identifier separate from `name`.
* `add_resource` and `add_sub_resource` functions allow new optional property `unique_id`
* `name` remains required but does not need to be unique for the entity type when using `unique_id`
* When `unique_id` is provided it will serve as the key for the resource in the `.resources` and `.sub_resources` dictionaries
* To use `unique_id` all resources must use `unique_id`
* When using `unique_id` name does not need to be unique for a resource
* Duplicate LocalRole permissions are removed before payload generation
* Optimization to payload size for unset entities
* Fix for boolean local user properties in payload

* Release and package publication