Analytics: Registry / Portal data sharing

The next phase of STR requires more support for audit and enforcement through more data analytics. This is beyond just standardized reports but allow for audit, sampling, fraud and abuse detection.

## Background
STR is comprised of 2 major services that should work in tandem. The 2 services are the STR Registry and the STR Data Sharing Portal.
**STR Registry** registers, approves and maintains all of the hosts, strata-hotels and platforms that can operate in the Province. It also manages the daily and registration level verifications of a valid permit to operate.
**STR Data Sharing Portal** is where platforms upload their host registrations in bulk, municipalities manages their rules such as a required business permit and where they can review registrations and submit enforcement action requests.

## Functionality re-assignment (out of scope of this epic)
There are some obvious workflows that should be better balanced between the services, to reduce duplication and make for a better UX. Some of that design would be helpful in targeting the analytics work.

## Data Sharing
### Currently
There is some limited data sharing via lookup APIs and extractions of CSV files. These meet the adhoc, non-self serve and realtime requirements but do not support more detailed analytics work.
### Future (Sept 25 onwards)
Initially more data should be shipped to the _STR Data Sharing Portal_ so that it can be combined with similar data being shared in bulk from the _platforms_ and _municipalities_.

### Activities
- [x] [Review options for large data sharing bcgov/entity#30671](https://github.com/bcgov/entity/issues/30671)
- [ ] Short write up on pros/cons of the options and share for approval
- [ ] [Documentation on database bcgov/entity#30723](https://github.com/bcgov/entity/issues/30723)