[Server v3] Sort, cleanup and uniformise SQL queries

[vxgmichel]

A cleanup of the SQL queries could be useful, in particular:

• check that consistent naming is used
• check that selected columns are actually used by the code
• see if some queries overlap

Some queries are also duplicated in different component modules. Instead, one component should probably expose a method to be used by the other components.

Another improvement would be to replace all the occurrences of such pattern:

FROM realm_topic
WHERE realm = { q_realm_internal_id(organization_id="$organization_id", realm_id="$realm_id") }

by:

FROM realm_topic
JOIN realm ON realm_topic.realm = realm._id
JOIN organization ON realm.organization = organization._id
WHERE realm.realm_id = $realm_id
AND organization.organization_id = $organization_id

At the moment both approaches are used, so it's a bit confusing to navigate between queries.

Another suggestion: internal ids for organization, user and device could be extracted during the checks common to all authenticated commands (see #7119 ). The same could also performed for the internal realm id for the realm commands. This would simplify a lot of SQL queries like the example above. There was already an attempt at implementing this here:

parsec-cloud/server/parsec/components/auth.py

Lines 46 to 67 in 11efa76

	@dataclass
	class AnonymousAuthInfo:
	organization_id: OrganizationID
	organization_internal_id: int
	@dataclass
	class InvitedAuthInfo:
	organization_id: OrganizationID
	token: InvitationToken
	type: InvitationType
	organization_internal_id: int
	invitation_internal_id: int
	@dataclass
	class AuthenticatedAuthInfo:
	organization_id: OrganizationID
	device_id: DeviceID
	device_verify_key: VerifyKey
	organization_internal_id: int
	device_internal_id: int