issues/239: max content width for Menu. Closes #239

[ryanjclark]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make?
I added the quick fix recommended in #239; allowing max-content for width and capping it at 280px.

It allows for long Kafka cluster names but won't ruin the UI in the case of a very long name.

Is there anything you'd like reviewers to focus on?
This feels good enough to close #239 while still allowing room for #528. Check out the picture to see how it looks.

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

[github-actions]

Hi ryanjclark! 👋

Welcome, and thank you for opening your first PR in the repo!

Please wait for triaging by our maintainers.

Please take a look at our contributing guide.