fix: PageTitleBar description

[hectordavis]

Closes #3785

Summary Fix of incorrect behavior of moving the PageTitleBar description to a tooltip when content was provided. It is now displayed below the title and only moved to the tooltip if the collapsed prop is passed. I've also added a feature requested by @JordanWSmith15 where the condensed variation of the title bar (with breadcrumbs) now contains the tooltip as well so the description can be easily accessed.

Change List (commits, features, bugs, etc)

• PageTitleBar logic fix to show description when content is provided and only move it to Tooltip if the condensed prop is true
• Tooltip with description added to condensed variation of page title bar to be easily accessed when header is "Dynamic" or "Condensed"
• Unit tests added and updated
• Snapshots updated
• PageTitleBar e2e tests fixed after changes

Acceptance Test (how to verify the PR)

• Check PageTitleBar stories and add a description to some of them. Unless condensed is set to true the description should be displayed below the title. For the DYNAMIC variation, it should be moved to the tooltip next to the current breadcrumb item when scrolling down. For the CONDENSED variation, it should only be in the tooltip next to the current breadcrumb item.

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

• Check if description below title is not rendered when it shouldn't like when scrolling down with DYNAMIC headerMode or when using CONDENSED headerMode

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	9185fad0a7747cd3a474408867479b7a2dffe714
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-addons-iot-react/deploys/646f52913d9484000870164b
😎 Deploy Preview	https://deploy-preview-3789--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 settings.