chore: resource registry

[MarioCadenas]

📚 Stack (3/3)

🏠 main (base)
│
└──▶ ✅ refactor-move-core-plugins
     │
     └──▶ ✅ plugin-manifest-definition
          │
          └──▶ 👉 resource-registry ◀ this PR

📝 Changes

• b7f9199 chore: resource registry

---

📖 About this stack

This PR is part of a stack of changes. Each PR in the stack builds on the one below it.

• ⬇️ Base: This PR is based on plugin-manifest-definition
• ⬆️ Next: This is the top of the stack

[pkosiec]

Overal LGTM, two small comments - please check them and address them (if applicable) here or in a follow-up PR 👍

[pkosiec]

BTW - do we need the public name for plugins if it's already in the static manifest? Or is it like an instance name which should vary when you instantiate the class multiple times?

[pkosiec]

Can we extract resource collection and validation to some separate methods? The logic here a bit makes it harder to read the high-level logic for registering plugins.

Like it was before:

    pluginInstance.validateEnv();

so now I can imagine, we'd have two calls: validation + collecting resources