Use Priority to override existing executor

[Lehmann-Fabian]

Since ServiceName.important is deprecated, I added support for the Priority annotation to work with the same behavior as other Nextflow Extension Points.

[netlify]

✅ Deploy Preview for nextflow-docs-staging ready!

Name	Link
🔨 Latest commit	bccc6f6
🔍 Latest deploy log	https://app.netlify.com/projects/nextflow-docs-staging/deploys/6846d74fb3ea840008e84c04
😎 Deploy Preview	https://deploy-preview-6135--nextflow-docs-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[bentsherman]

Plugins.getPriorityExtensions() is normally used to load plugins in a priority-aware manner, and should ideally be used here as well. Though I'm not sure why the plugin manager is provided here instead of just using Plugins

[Lehmann-Fabian]

I think we can merge both constructors now as the manager isn't used anymore. What do you think?

[pditommaso]

The ServiceName.important is deprecated, but there's no plan to remove it. Therefore I don't see a parallel logic necessary

[Lehmann-Fabian]

Thank you for the clarification. However, I generally assumed that you eventually will remove deprecated elements. Therefore, I believe it's good practice to support both the deprecated and the new logic in parallel. This allows plugins to continue using important as long as it's available and ensures a smooth transition once it's removed, maintaining backward compatibility. This new approach is also consistent with how other extension points are currently managed.
If there is no plan to deprecate the important feature, should I remove the @Deprecated annotation?