Navigation Submenu: Fix color handling and inheritance

[yogeshbhutkar]

What, Why & How?

Testing Instructions for Keyboard

1. Navigate to a Post/Page edit screen.
2. Create a Navigation Block.
3. Try setting up different permutations for text and background properties along with custom colors.
4. Notice the bugs mentioned in the issue are now fixed.

Screencasts

The following are the expected outcomes that the submenu block should abide by.

If the navigation block has either a background or a text color assigned, and there's no color provided for the submenu & overlay text or submenu & overlay background, then navigation blocks color should be inherited. ( ✅ )

If the navigation block has specified a color, but, the submenu parent has also specified a color (background and text ), the submenu container should still inherit the color from the navigation block. ( ✅ )

If submenu & overlay text or submenu & overlay background values are provided, these should overwrite the values of navigation block. ( ✅ )

if only submenu's color and background value are passed, then it shouldn't override the value of the submenu container. Container's values must be either inherited from navigation or from the dedicated submenu control options on navigation. ( ✅ )

Closes: #68350

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: yogeshbhutkar <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.