Add settings to mark cryptographic algorithms in vpn customer gateways as excluded or obsolete

[abh1sar]

Description

This PR introduces several configuration settings using which an operator can mark certain cryptographic algorithms and parameters as excluded or obsolete for VPN Customer Gateway creation for Site-to-Site VPN.

Cloud providers following modern security frameworks (e.g., ISO 27001/27017) are required to enforce and communicate approved cryptographic standards. CloudStack currently accepts several weak or deprecated algorithms without guidance to users. This PR closes that gap by giving operators explicit control over what is disallowed vs discouraged, improving security posture without breaking existing deployments.

These settings are:

1. vpn.customer.gateway.excluded.encryption.algorithms
2. vpn.customer.gateway.excluded.hashing.algorithms
3. vpn.customer.gateway.excluded.ike.versions
4. vpn.customer.gateway.excluded.dh.group
5. vpn.customer.gateway.obsolete.encryption.algorithms
6. vpn.customer.gateway.obsolete.hashing.algorithms
7. vpn.customer.gateway.obsolete.ike.versions
8. vpn.customer.gateway.obsolete.dh.group

Details :

1. Excluded parameters are not shown to the Users in the Create and Update VPN Customer Gateway forms.
2. Obsolete parameters are shown with a warning
3. If a VPN gateway is already using an excluded or obsolete parameter:
   a. A warning icon is displayed near to it's name with a message to change the obsolete parameter.
   b. The Update VPN gateway form shows the setting with a warning to change it.
4. listVpnCustomerGateways api returns two new fields containsobsoleteparameters and containsexcludedparameters which tells whether an existing gateway is containing obsolete or excluded.
5. A new field in the listCapabilities API response contains the list excluded and obsolete vpn customer gateway parameters, only if set.

Documentation PR : apache/cloudstack-documentation#605

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):

### How Has This Been Tested?

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 3.57%. Comparing base (2600965) to head (6bfda8a).
⚠️ Report is 7 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (2600965) and HEAD (6bfda8a). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (2600965)	HEAD (6bfda8a)
unittests	1	0

Additional details and impacted files

@@              Coverage Diff              @@
##               main   #12193       +/-   ##
=============================================
- Coverage     17.57%    3.57%   -14.00%     
=============================================
  Files          5913      447     -5466     
  Lines        529427    37645   -491782     
  Branches      64677     6934    -57743     
=============================================
- Hits          93024     1347    -91677     
+ Misses       425940    36132   -389808     
+ Partials      10463      166    -10297     

Flag	Coverage Δ
uitests	3.57% <ø> (-0.02%)	⬇️
unittests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[abh1sar]

@blueorangutan package

[blueorangutan]

@abh1sar a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 15920

[nvazquez]

@abh1sar can you please target this branch against main branch?