Add support for registry scoped RPSL pk

[jwbensley]

A 2nd attempt at adding a registry scope for an AS-SET or ASN.

Last time it was agreed that having a dedicated type was a better way to go, to avoid string matching/parsing. That is what I have done this time, although there is no 100% avoiding string matching/parsing;

• The GrahphQL list type needs to be a list of a single type, so it is now a list of the new type (either a registry scoped ASN type for asnPrefixes or a registry scoped SET name for asSetPrefixes and recursiveSetMembers, but the registry scope is optional and defaults to None to support backwards compatibility).
• Even if lists of two types were supported, we'd need to string match/parse each entry to work out which type was input by the user, and then we'd end up with two types that have to be handled differently. One type which can optionally be registry scoped is cleaner I think.
• All docs and tests updated.
• Full discloser; Copilot is always on in my code editor auto-completing as I write, so some percentage of this is AI generated, but I proof read everything, ensured all tests and docs were updated, and passing, before opening the PR.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[jwbensley]

I added more unit tests, I see 100% tests passing and 100% test coverage.
I don't know why the integration tests are failing, it doesn't seems to relate to the files I've changed. I'm also struggling to get the integration tests to run locally.

pytest --cov-report term-missing:skip-covered --cov=irrd -x -vv irrd

...
---------- coverage: platform linux, python 3.12.3-final-0 -----------
Name    Stmts   Miss  Cover   Missing
-------------------------------------
TOTAL   11549      0   100%

125 files skipped due to complete coverage.

================================================================================== 816 passed, 43 warnings in 118.31s (0:01:58)

[jwbensley]

Ready @mxsasha