Addressescoder/internal#317.## ChangesRequirements are quoted below:> how many orgs does deployment haveAdds the Organization entity to telemetry.> ensuring resources are associated with orgsAll resources that reference an org already report the org id totelemetry. Adds a test to check that.> whether org sync is configuredAdds the `IDPOrgSync` boolean field to the Deployment entity.## Implementation of the org sync checkWhile there's an `OrganizationSyncEnabled` method on the IDPSyncinterface, I decided not to use it directly and implemented acounterpart just for telemetry purposes. It's a compromise I'm not happyabout, but I found that it's a simpler approach than the alternative.There are multiple reasons:1. The telemetry package cannot statically access the IDPSync interfacedue to a circular import.2. We can't dynamically pass a reference to the`OrganizationSyncEnabled` function at the time of instantiating thetelemetry object, because our server initialization logic depends on thetelemetry object being created before the IDPSync object.3. If we circumvent that problem by passing the reference as aninitially empty pointer, initializing telemetry, then IDPSync, thenupdating the pointer to point to `OrganizationSyncEnabled`, we have torefactor the initialization logic of the telemetry object itself toavoid a race condition where the first telemetry report is performedwithout a valid reference.I actually implemented that approach in#16307, but realized I'm unable tofully test it. It changed the initialization order in the servercommand, and I wanted to test our CLI with Org Sync configured with apremium license. As far as I'm aware, we don't have the tooling to dothat. I couldn't figure out a way to start the CLI with a mock license,and I didn't want to go down further into the refactoring rabbit hole.So I decided that reimplementing the org sync checking logic is simpler.(cherry picked from commit92d22e2)

Closescoder/internal#323This PR adds an `email` field to the `data.owner` payload for workspacecreated and workspace manually updated notifications, as well as useraccount created/activated/suspended.(cherry picked from commitf651ab9)

…on (#16315)(cherry picked from commit92a490b)

Addressescoder/nexus#175.## Changes- Adds the `telemetry_items` database table. It's a key value store fortelemetry events that don't fit any other database tables.- Adds a telemetry report when HTML is served for the first time in`site.go`.(cherry picked from commit2ace044)

(cherry picked from commit2371153)

…efault (#16337)(cherry picked from commitb256b20)

(cherry picked from commit0e2ae10)

Addressescoder/nexus#116.## Core ConceptSend one final telemetry report after the user disables telemetry withthe message that the telemetry was disabled. No other information aboutthe deployment is sent in this report.This final report is submitted only if the deployment ever had telemetryon.## Changes1. Refactored how our telemetry is initialized.2. Introduced the `TelemetryEnabled` telemetry item, which allows todecide whether a final report should be sent.3. Added the `RecordTelemetryStatus` telemetry method, which decideswhether a final report should be sent and updates the telemetry item.4. Added tests to ensure the implementation is correct.(cherry picked from commita68d115)