made env upload category more specific

[Gkrumbach07]

closes: #1206

Description

When secret upload was added, the category for the env upload was "upload" for both secrets and config maps. B/c the upload for secret was checked first, uploaded envs would always be created as secrets.

How Has This Been Tested?

create a workbench with an uploaded config map and make sure it is created as a config map and not a secret

Test Impact

no impact

Request review criteria:

• The commits have meaningful messages (squashes happen on merge by the bot).
• 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.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work
• The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)
  no ux changes

[lucferbux]

/lgtm

Tested and its working fine:

[lucferbux]

/assign @andrewballantyne

[andrewballantyne]

I can't upload secrets 🤔

Was this broken by your code? -- Yup. Because we didn't implement the reference to Secret UPLOAD when we did it originally -- https://github.com/opendatahub-io/odh-dashboard/blob/main/frontend/src/pages/projects/screens/spawner/spawnerUtils.ts#L323

[lucferbux]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewballantyne, lucferbux

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 [andrewballantyne]

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