fix(core): remove hardcoded style from ngx for toolbar component

[manu-kr]

Please provide a link to the associated issue.

Part of #5025

Please provide a brief summary of this pull request.

Remove style from ngx lib as part of style cleanup for toolbar component.

Breaking Changes:

• Added New Directory for toolbar over flow as part of style cleanup
  fd-toolbar-overflow-button, fd-toolbar-overflow-button-menu

Before

Toolbar overflow button

<button fd-toolbar-item fd-button label="Button" [compact]="true"></button>

After

Toolbar overflow button

<button fd-toolbar-item fd-button fd-toolbar-overflow-button label="Button" [compact]="true"></button>

Before

Toolbar overflow menu button

<button fd-toolbar-item fd-button label="Button" [fdMenu]="true" [compact]="true"></button>

After

Toolbar overflow menu button

<button fd-toolbar-item fd-button fd-toolbar-overflow-button fd-toolbar-overflow-button-menu label="Button" [fdMenu]="true" [compact]="true"></button>

Before

After

Please check whether the PR fulfills the following requirements

• the commit message 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

Documentation checklist:

• [NA] update README.md
• Breaking Changes Wiki
• Documentation Examples
• Stackblitz works for all examples

[netlify]

✔️ Deploy Preview for fundamental-ngx ready!

🔨 Explore the source changes: b397803

🔍 Inspect the deploy log: https://app.netlify.com/sites/fundamental-ngx/deploys/612e53e8d428440007651f2f

😎 Browse the preview: https://deploy-preview-6396--fundamental-ngx.netlify.app

[lgtm-com]

This pull request fixes 2 alerts when merging 0ae4bfa into 52d8f88 - view on LGTM.com

fixed alerts:

• 2 for Unused variable, import, function or class

[github-actions]

This pull request is stale because it has been open 2 days with no activity. Remove stale label or comment or this will be closed in 3 days

[N1XUS]

Please fix @Smiranin comments

[lgtm-com]

This pull request fixes 2 alerts when merging 68dd280 into fe8a11f - view on LGTM.com

fixed alerts:

• 2 for Unused variable, import, function or class

[lgtm-com]

This pull request fixes 2 alerts when merging a76dd60 into bac63c1 - view on LGTM.com

fixed alerts:

• 2 for Unused variable, import, function or class

[lgtm-com]

This pull request fixes 2 alerts when merging 259828e into c0a1e58 - view on LGTM.com

fixed alerts:

• 2 for Unused variable, import, function or class

[InnaAtanasova]

The Breaking changes examples serve no purpose to the user. They don't need screenshots of how the component looked before and now, they need code examples of what was changes so they can modify their code as fast/easily as possible.

[manu-kr]

The Breaking changes examples serve no purpose to the user. They don't need screenshots of how the component looked before and now, they need code examples of what was changes so they can modify their code as fast/easily as possible.

Updated breaking changes.

[lgtm-com]

This pull request fixes 2 alerts when merging 6f68c0f into c0a1e58 - view on LGTM.com

fixed alerts:

• 2 for Unused variable, import, function or class

[lgtm-com]

This pull request fixes 2 alerts when merging 19fca8e into c0a1e58 - view on LGTM.com

fixed alerts:

• 2 for Unused variable, import, function or class

[puru-hk]

Looks fine

[lgtm-com]

This pull request fixes 2 alerts when merging b397803 into ad03ec6 - view on LGTM.com

fixed alerts:

• 2 for Unused variable, import, function or class

[dimamarksman]

@manu-kr shouldn't we put Breaking Changes in the PR's description?

[manu-kr]

@manu-kr shouldn't we put Breaking Changes in the PR's description?

@dimamarksman As of now we not added Breaking Changes in description, Now i added it PR description as well.