feat() Map domain errors to gRPC status codes

[D-VR]

• Added domain sentinels (provisioning failed, Pulumi canceled, filesystem errors, expired challenge, pool exhausted, renew-not-allowed, lock contention, validation failed) and mapped them to appropriate gRPC codes.
• Enforce numeric challenge IDs (CTFd compatibility).
• Improved filesystem/Pulumi error handling to avoid opaque 500s; provisioning cancel now returns Aborted instead of generic internal errors.

Why: To stop the gRPC gateway from emitting generic 500s and give downstream (CTFd plugin/UI) actionable error codes/messages. See: ctfer-io/ctfd-chall-manager#238

Issues: Partially fixes ctfer-io/ctfd-chall-manager#232; addresses ctfer-io/ctfd-chall-manager#225.

I accept the code of conduct.

[pandatix]

Why wanting to enforce numeric IDs ?
Chall-Manager is agnostic of CTFd, thus has never been a requirement (for numerics). The string type enables support for downstream services to provide alternative identifier formats, e.g. GUID.

[D-VR]

Why wanting to enforce numeric IDs ? Chall-Manager is agnostic of CTFd, thus has never been a requirement (for numerics). The string type enables support for downstream services to provide alternative identifier formats, e.g. GUID.

when CM had string IDs (created them directly via the CM API during testing), the plugin tried to link to /admin/challenges/ and blew up because CTFd challenge IDs are numeric PKs. But if you want CM to be agnostic to CTFd I can remove that check again.

The CM plugin PR already prevents the admin page from crashing even if string IDs exist in CM.

[pandatix]

Yeah I would prefer to stick with strings for IDs here 👍

[D-VR]

Yeah I would prefer to stick with strings for IDs here 👍

done! 😄

[pandatix]

Overall good, did not run it yet. There are some improvements to be made first then it will be tested more thoroughly 😉

[D-VR]

I have added the requested changes, for error traces I will do a new PR if I get to it :)