[enterprise-4.18] : config data key cannot be user defined

[openshift-cherrypick-robot]

This is an automated cherry-pick of #85543

/assign dfitzmau

[openshift-ci-robot]

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-44349 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh: /jira refresh

/retitle [enterprise-4.18] : config data key cannot be user defined

In response to [this](https://github.com/openshift/openshift-docs/pull/85555): >This is an automated cherry-pick of #85543 > >/assign dfitzmau Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci-robot]

@openshift-ci-robot: This pull request references Jira Issue OCPBUGS-44349, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-44349 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/openshift-docs/pull/85555#issuecomment-2504408997): >@openshift-cherrypick-robot: Could not make automatic cherrypick of [Jira Issue OCPBUGS-44349](https://issues.redhat.com//browse/OCPBUGS-44349) for this PR as the target version is not set for this branch in the jira plugin config. Running refresh: >/jira refresh > > >/retitle [enterprise-4.18] : config data key cannot be user defined > >

> >In response to [this](https://github.com/openshift/openshift-docs/pull/85555): > >>This is an automated cherry-pick of #85543 >> >>/assign dfitzmau > > >Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository. >

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: No Jira issue is referenced in the title of this pull request. To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to [this](https://github.com/openshift/openshift-docs/pull/85555): >This is an automated cherry-pick of #85543 > >/assign dfitzmau Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci[bot]]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).