[Dashboard] Don't make controls overflow outside of screen horizontally

[mbondyra]

Summary

Fixes dashboard controls (small, medium, large sizes) overflowing horizontally outside their container when the container is narrower than the control's fixed width.

Problem: Controls with fixed widths (e.g., controlFrameWrapper--large = 800px) would overflow their container because minWidth takes precedence over maxWidth in CSS. Adding maxWidth: 100% doesn't work when minWidth is larger than the container.

Solution: Use CSS min() function for both width and minWidth to pick the smaller value between the fixed pixel width and 100% of the container:

• controlFrameWrapper--small: min(224px, 100%)
• controlFrameWrapper--medium: min(400px, 100%)
• controlFrameWrapper--large: min(800px, 100%)

how to test

1. Open a dashboard with controls in a narrow container (e.g., Dashboard Agent sidebar or just resize the window)
2. Verify that large controls no longer overflow horizontally
3. Verify that controls still maintain their intended widths when the container is wide enough

Before:

After:

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

• See some risk examples
• ...

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 575dc04

Failed CI Steps

• FTR Configs #100

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
controls	526.1KB	526.2KB	+78.0B
dashboard	845.9KB	846.0KB	+78.0B
discover	1.6MB	1.6MB	+78.0B
infra	1.3MB	1.3MB	+78.0B
maps	3.2MB	3.2MB	+78.0B
observability	2.2MB	2.2MB	+78.0B
securitySolution	11.5MB	11.5MB	+78.0B
slo	1.1MB	1.1MB	+78.0B
triggersActionsUi	1.8MB	1.8MB	+78.0B
total			+702.0B

History

• 💔 Build #419186 failed b17af43
• 💔 Build #419115 failed 39ead54