feat: new content density mechanism

[N1XUS]

Description

• Migrated content density logic from fundamental-styles;
• Removed all '[component]--compact' classes in favour of unified 'is-compact' and 'is-condensed';
• Updated unit test selectors;
• Updated e2e test selectors;
• Removed changeDetector from contentDensityIObserver and migrated all listeners of contentDensityObserver.isCompact to async contentDensityObserver.isCompact$;
• closes bug: platform select docs page prevents tab keydown event #9627
• closes bug(core,platform): select focused button is not by the guidelines #9628
• closes Shellbar input styling broken in compact mode #9607
• closes Platform Table: Navigable row indicator column not clickable #9592

Please check whether the PR fulfills the following requirements

During Implementation

1. Visual Testing:

• visual misalignments/updates
• check Light/Dark/HCB/HCW themes
• RTL/LTR - proper rendering and labeling
• responsiveness(resize)
• Content Density (Cozy/Compact/(Condensed))
• States - hover/disabled/focused/active/on click/selected/selected hover/press state
• Interaction/Animation - open/close, expand/collapse, add/remove, check/uncheck
• Mouse vs. Keyboard support
• Text Truncation

2. API and functional correctness

• check for console logs (warnings, errors)
• API boundary values
• different combinations of components - free style
• change the API values during testing

3. Documentation and Example validations

• missing API documentation or it is not understandable
• poor examples
• Stackblitz works for all examples

4. Accessibility testing
5. Browser Testing - Edge, Safari, Chrome, Firefox

PR Quality

• the commit message(s) follows the guideline:
  https://github.com/SAP/fundamental-ngx/blob/main/CONTRIBUTING.md
• tests for the changes that have been done
• all items on the PR Review Checklist are addressed :
  https://github.com/SAP/fundamental-ngx/wiki/PR-Review-Checklist
• Run npm run build-pack-library and test in external application
• update README.md
• Breaking Changes Wiki

[netlify]

✅ Deploy Preview for fundamental-ngx ready!

Name	Link
🔨 Latest commit	fcc3aa2
🔍 Latest deploy log	https://app.netlify.com/sites/fundamental-ngx/deploys/642c355dd68c1d000865abf6
😎 Deploy Preview	https://deploy-preview-9596--fundamental-ngx.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.

[github-actions]

Visit the preview URL for this PR (updated for commit fcc3aa2):

https://fundamental-ngx-gh--pr9596-feat-new-content-den-uw61g162.web.app

_{(expires Fri, 07 Apr 2023 14:45:22 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 41b993ee8e451bd7c6770b342ce142dc886eacff}

[g-cheishvili]

Nice simplification, now basically none of the HTML usages are needed and you can just use it

[mikerodonnell89]

Core menu items are not responding to density changes. Also same with combobox, multicombobox, multiinput, i suspect all the same reasons:

Screen.Recording.2023-03-28.at.2.56.30.PM.mov

[mikerodonnell89]

Datepicker items still showing in cozy when everything else is compact - could be just a popover contents thing in general?

[mikerodonnell89]

Specs state that the feed input button should always be used in cozy mode

[mikerodonnell89]

Input group and form message focus outlines are behaving odd on this PR but not on the current netlify build for the latest main: https://fundamental-ngx.netlify.app/#/platform/input-group.

From the platform input group docs, in this first screenshot, after clicking submit, the whole docs page gets focused

From the platform input group docs, here we see the whole input gets a focus outline

This is from core input group:

[N1XUS]

@mikerodonnell89 Thank you for your review! Please re-check, all items has been addressed.

[mikerodonnell89]

Not caused by this PR, but, possibly related and fixable here? #9607

[mikerodonnell89]

There are a few focus outline issues coming from a recent fundamental-styles RC release so I think we need to hold off merging this (or updating fundamental-styles in general) until those issues can be fixed

[N1XUS]

Not caused by this PR, but, possibly related and fixable here? #9607

Yes, it is reproducible in main too, so it is not comming from this PR