Add migration for hardware profiles

[Gkrumbach07]

https://issues.redhat.com/browse/RHOAIENG-17224

Description

follows: https://docs.google.com/document/d/1VtvU2gOhNU_aW0xol0SquWGlSGvh2o_G7jgpQzGwDa4/edit?tab=t.0#heading=h.9i6jzposf7xi
Adds the the following

• New useMigratedHardwareProfiles
  • creates migration/fake hardware profiles from...
    • accelerator profiles
      • creates 2: one for notebooks, one for serving
      • notebooks gets notebook only toleration if enabled
    • container size from dashboard config
      • notebooks and serving
      • notebooks gets notebook only toleration if enabled
  • returns all fake and real hardware profiles
  • also returns a way to get a MigrationAction
    • this has info and callbacks to delete the source and give details for the migrated
• introduces visible in concept for hardware profiles
  • new field in manage page
  • is used to hide/show certain hardware profiles is certain areas
  • has a hook to abstract it for use
  • new column in table
• makes maxCount optional in CRD
• adds labels on hardware profile table to indicate there are translated profiles
• adds warnings on delete for translated profiles
  • on delete, it will delete the source
• adds warnings on edit of translated resource
  • will delete source
  • will create new hardware profile
  • will also create additional profiles if the source had more than dependent like accelerator profiles

How Has This Been Tested?

1. create hardware profiles, accelerator profiles, and populate dashboard config with notebook and model serving container sizes
2. try editing and saving both types of translated hardware profiles
3. try deleting both types
4. edit visible in and make sure it is reflected in notebooks areas and serving runtime areas

Test Impact

added units tests

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from gkrumbach07. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Gkrumbach07]

Some Images @vconzola @kaedward

Table details

** New visibility param**

Edit warnings

Delete warnings

[pnaik1]

@Gkrumbach07 , Do we need alert message when we duplicating a simulted hardwareprofiles?

[pnaik1]

tested all the functionality works well except
the deletion of simulated hardwareProfiles takes more time to reflect the changes in the HardwareProfile table