Docs: Where/how to document the backend key-alias mapping feature introduces in #6245

[edan-bainglass]

#6245 introduced a key-alias mapping in the backend for various QueryBuilder keys.

aiida-core/src/aiida/storage/psql_dos/orm/querybuilder/main.py

Lines 42 to 70 in 8ac6424

	PROJECT_MAP = {
	'db_dbauthinfo': {
	'pk': 'id',
	'computer_pk': 'dbcomputer_id',
	'user_pk': 'aiidauser_id',
	},
	'db_dbnode': {
	'pk': 'id',
	'dict': 'attributes',
	'computer_pk': 'dbcomputer_id',
	'user_pk': 'user_id',
	},
	'db_dbcomputer': {
	'pk': 'id',
	},
	'db_dbgroup': {
	'pk': 'id',
	'user_pk': 'user_id',
	},
	'db_dbcomment': {
	'pk': 'id',
	'user_pk': 'user_id',
	'node_pk': 'dbnode_id',
	},
	'db_dblog': {
	'pk': 'id',
	'node_pk': 'dbnode_id',
	},
	}

This takes care of all known aliasing required for the postgresql backend, leaving the key aliasing mechanism available strictly for new data types (for plugin developers). Note that currently the map is in the postgresql backend, but the idea is that all backends should implement a similar mapping, with their respective aliases, so the frontend remains as is. With the map in place. users may now use the frontend keys in the QueryBuilder, so for example, use pk, not id (though still valid).

With that in mind, I propose we update the codebase (and documentation) accordingly w.r.t this mapping to promote the use of the frontend keys only, i.e. no mentions of id (for example).

[edan-bainglass]

The above was discussed during the 04.04.2024 AiiDA core developer meeting. Consensus is approval. I'll scan the code, verify the projections catch everything, and update the docs accordingly. Further discussion to follow in the associated PR.

Will also take a look at the tutorials.