feat: close header side nav on navigation

[hectordavis]

Closes https://jsw.ibm.com/browse/GRAPHITE-67441

Summary

• Close icon added when hamburger button is clicked to open side nav
• Close side nav functionality added to be called when clicking a side nav item

Change List (commits, features, bugs, etc)

• New closeSideNavOnNavigation prop added to SuiteHeader to enable side nav to close when clicking one of its items.
• Recursive function added to add the feature above on each item
• isActive prop passed from Header to HeaderMenuButton in order to show the Close menu icon

Acceptance Test (how to verify the PR)

1. Go to SuiteHeader > Legacy (single workspace only) > Header with side nav story and click the hamburger icon to check if the Close icon is displayed. Then click the close icon to see if it changes back to hamburger menu.
2. In the same story, check the Close side nav on navigation knob then open the side nav again by clicking the hamburger menu, then click "Home" and check if the side nav closes. Repeat the same but now for Dashboard > Link 1 item and check if the side nav closes after clicking.

Regression Test (how to make sure this PR doesn't break old functionality)

• Uncheck the Close side nav on navigation knob and check if the side nav remains open after clicking the items

Things to look for during review

• [ ] Make sure all references to iot or bx class prefix is using the prefix variable
• [ ] (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
• [ ] UI should be checked in RTL mode to ensure the proper handling of layout and text.
• [ ] All strings should be translatable.
• [ ] The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
• [ ] Unit test should be written and should have a coverage of 90% or higher in all areas.
• [ ] All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
• [ ] Changes or new components should either write new or update existing documentation.
• [ ] PR should link and close out an existing issue

[netlify[bot]]

✅ Deploy Preview for carbon-addons-iot-react ready!

Name	Link
🔨 Latest commit	f5f69b411cfc9b1580f534ca295136a57fa05c2f
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-addons-iot-react/deploys/6511aaa53aa35600084ebe86
😎 Deploy Preview	https://deploy-preview-3826--carbon-addons-iot-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.