Add Accelerator section in Admin Panel and feature flag

[dpanshug]

Closes: #1372

Description

Added new feature flag disableAccelerators and new section in the admin panel for accelerators.

How Has This Been Tested?

1. Add accelerator profile crd to your cluster, from odh-dasboard/manifests/crd/acceleratorprofiles.opendatahub.io.crd.yaml
2. Open ODH dashboard with clusteradmin login
3. In the sidebar, under setting section you can find Accelerator Profiles.

Note: This PR only provides empty state of the page, so make sure you don't have any AcceleratorProfile operand in your cluster.

Test Impact

Integration testing: To test Empty State of no Accelerator profile and created storybook too.

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• 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 tests & storybook 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 (find relevant UX in the SMEs section).

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

cc @yannnz

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[dpanshug]

/test all

[Gkrumbach07]

@kaedward In the mocks you gave concern on the wording of the empty state, The empty state is for admins to add accelerator profile CRs (gpus). Accelerator profiles are used to sync the use of gpus in the UI to the physical hardware in the cluster. Essentially an admin would go add an accelerator profile after they configured actual accelerators in the openshift console.

[Gkrumbach07]

please add tests too @dpanshug

[Gkrumbach07]

A few things and then should be good to go

[Gkrumbach07]

/lgtm

@andrewballantyne this is ready for your review/approval

[Gkrumbach07]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: Gkrumbach07

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

The pull request process is described 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

[kaedward]

@kaedward In the mocks you gave concern on the wording of the empty state, The empty state is for admins to add accelerator profile CRs (gpus). Accelerator profiles are used to sync the use of gpus in the UI to the physical hardware in the cluster. Essentially an admin would go add an accelerator profile after they configured actual accelerators in the openshift console.

Thanks for the details, @Gkrumbach07 ! I think my problem was more with the phrasing - usually we wouldn't tell a user to go ask someone about something if we don't know for certain who that person is or if it is the current user. It's different if we're asking them to go ask their admin for some permission, but here we're not sure. This is based on @yannnz's comment in the mocks, which was 4 months ago so is probably outdated: " I believe they need to check the availability of accelerators in cluster, although it’s unclear who they should check with."

LMK if this is outdated and the info in the screenshot above is correct, and I can write another suggestion. For now though, I would recommend something more like this:

"No accelerator profiles yet
To get started, create an accelerator profile that corresponds with an available accelerator in your OpenShift cluster.
[Create accelerator profile]"

This is more straight-forward and allows the user to figure out who they need to talk to (if anyone). I also removed the "please" which we try to avoid, and updated the button to "Create" instead of "Add" since we refer to this as "Create" everywhere else. Please LMK what you think!