Ownership of the `ID_ALLOCATION_TOKEN`

The allocate-definitive-ids.yaml workflow, used to automatically reserialise the -edit file if needed after every PR and replace temporary IDs by definitive IDs, requires an authorisation token to work (since it has to write to the repository).

Currently, I am the owner of that authorisation token, meaning the workflow runs on my behalf.

As I will no longer be professionally involved with Uberon at the end of this week, Uberon editors/stakeholders might want to consider using someone else’s account (ideally someone more permanently associated with Uberon, for as much as anything can be said to be “permanent” in this world).

The current token expires in September 2026, so a decision does not need to be taken immediately. If no decision has been taken by then, I will simply renew the token so that nothing breaks, and the workflow will continue to forever be associated with my account.

(This is assuming that you are fine with me keeping writing access to the repository despite no longer officially working on Uberon. If you are not fine with that, then the ownership of the token must be transferred before my rights to the repository are revoked.)

The same issue will also arise in CL for the same reason.