fix: allow third-party backup provider plugins via configurable allowed list

[yigitbasalma]

Description

Currently, the backup.framework.provider.plugin setting validates against a hardcoded list of plugins (dummy, veeam, networker, nas). This prevents third-party backup provider plugins from being registered and used in CloudStack, even when the plugin is correctly implemented and deployed.

This PR introduces a new configuration key backup.framework.provider.plugin.allowed that contains a comma-separated list of allowed backup provider plugins. Administrators can extend this list to include third-party plugins without modifying CloudStack source code.

Default value maintains full backward compatibility with existing plugins.

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

N/A

How Has This Been Tested?

• All existing unit tests pass (714 tests, 0 failures, 0 errors)
• Verified backward compatibility: default value of backup.framework.provider.plugin.allowed includes all existing plugins (dummy, veeam, networker, nas)
• Verified third-party plugin registration works by adding a custom plugin name to the allowed list

How did you try to break this feature and the system with this change?

• Tested with invalid plugin name — proper error message returned with list of allowed plugins
• Tested with empty allowed list — validation correctly rejects all plugin names
• Tested with existing plugin names (dummy, veeam, networker, nas) — all work as before

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache CloudStack community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md)
Here are some useful points:

• In case of a new feature add useful documentation (raise doc PR at https://github.com/apache/cloudstack-documentation)
• Be patient and persistent. It might take some time to get a review or get the final approval from the committers.
• Pay attention to the quality of your code, ensure tests are passing and your PR doesn't have conflicts.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Issues, Mailing list and Slack.
• Be sure to read the CloudStack Coding Conventions.
  Apache CloudStack is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@cloudstack.apache.org (https://cloudstack.apache.org/mailing-lists.html)
  Slack: https://apachecloudstack.slack.com/