Fix submenu text color

[JarunMadhesh]

Hey, I just made a Pull Request!

Fix for #24315
Made title and subtitles of sub menu's color editable using theme palette

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)
• All your commits have a Signed-off-by line in the message. (more info)

[backstage-goalie]

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
@backstage/core-components	packages/core-components	patch	v0.14.7-next.2
@backstage/theme	packages/theme	patch	v0.5.4-next.0

[backstage-goalie]

Thanks for the contribution!
All commits need to be DCO signed before they are reviewed. Please refer to the the DCO section in CONTRIBUTING.md or the DCO status for more info.

[github-actions]

Uffizzi Ephemeral Environment - Virtual Cluster

Your cluster pr-24366 was successfully created. Learn more about Uffizzi virtual clusters
To connect to this cluster, follow these steps:

1. Download and install the Uffizzi CLI from https://docs.uffizzi.com/install
2. Login to Uffizzi, then select the backstage account and project:

uffizzi login

Select an account: 
  ‣ backstage
    jdoe

Select a project or create a new project: 
  ‣ backstage-6783521

3. Update your kubeconfig: uffizzi cluster update-kubeconfig pr-24366 --kubeconfig=[PATH_TO_KUBECONFIG]
   After updating your kubeconfig, you can manage your cluster with kubectl, kustomize, helm, and other tools that use kubeconfig files: kubectl get namespace --kubeconfig [PATH_TO_KUBECONFIG]

Access the backstage endpoint at https://backstage-default-pr-24366-c5094.uclusters.app.uffizzi.com

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[vinzscam]

Thank you! Make sure to run yarn build:api-reports locally and commit the changed files and remember to sign your commits to make the DCO check pass

[JarunMadhesh]

@vinzscam I ran yarn build:api-reports and commited the changes with proper singing.
DCO is failing as I missed to sign the first 2 commits. Is there anything that I can do for that?

[clanghout]

@JarunMadhesh It looks like the first 2 commits you made were not signed off. In order to reach those, you can run git rebase --signoff HEAD~7. I think you will run into some conflicts. If you fix those and finish the rebase, you can force push the changes to your branch and the MR should be good.

[JarunMadhesh]

Done @clanghout @vinzscam DCO has passed, but test and verify WFs are not running. What do i do?

[benjdlambert]

I think it's because this branch has some conflicts.