Improve Rightsizing Preferences

** I'm using EBS as an example, but this would apply for all the services. ** 
Introduce the capability to customize Amazon EBS volume recommendations in Cloudability’s rightsizing preferences, allowing users to exclude specific EBS volume types (e.g., `st1`, `sc1`) from optimization and rightsizing suggestions.

Why Is It Useful?
    •    Alignment with Business Policies: Many organizations have strict storage policies or technical requirements that mandate the use (or avoidance) of certain EBS volume types. Providing exclusion options allows teams to enforce architectural and compliance standards through automation.
    •    Improved Recommendation Quality: Excluding non-preferred or unsupported EBS types (like `st1` for throughput-optimized HDD or `sc1` for cold HDD) prevents Cloudability from suggesting rightsizing actions that are not relevant, actionable, or cost-effective for the customer’s specific workload or storage strategy.
    •    Operational Efficiency: Reduces manual review and overrides, saving engineering and FinOps teams significant time in validating and implementing recommendations.

Who Would Benefit From It?
    •    Enterprise Customers: Large organizations managing hundreds to thousands of volumes across multiple regions, such as enterprise clients in finance (e.g., Itaú Unibanco), retail, or technology, who have standardized on certain EBS types for reliability, performance, or compliance reasons.
    •    FinOps and Cloud Center of Excellence Teams: These teams can more easily enforce policy-driven governance on storage footprint and reduce cloud waste by focusing only on relevant recommendations.
    •    Cloud Architects and Sysadmins: By automatically filtering out inapplicable options, architects are empowered to maintain best practices without manual intervention.

How Should It Work?
    •    User Interface Enhancement:
          •    Extend the rightsizing preferences UI within Cloudability’s Storage Recommendations to include a multiselect option for EBS volume type exclusions.
          •    Supported types should at least include `gp3`, `gp2`, `io1`, `io2`, `st1`, and `sc1`.
    •    Recommendation Engine Logic:
          •    When generating EBS optimization recommendations, the engine should skip excluded volume types entirely, ensuring only actionable and relevant options are presented.
    •    API & Reporting Impact:
          •    Update API endpoints and exported reports to honor these user-defined exclusions, giving a consistent experience across dashboards and integrations.