Fix share to space flyout sizing

[jportner]

Overview

In #128946 I fixed some UX problems in the "Share to space" flyout (formerly "Assign to space" flyout). Those changes made it more resilient when rendered on smaller and larger screens.

However, there are three situations where a warning callout can be displayed at the top of the flyout:

1. If an object has not yet been shared anywhere
2. If an object is shared to All Spaces and the user doesn't have privileges to change that
3. If one or more destination spaces have legacy URL alias conflicts

Today I noticed that, due to my recent changes, these callouts were unintentionally stretching vertically when the viewport is tall. This PR fixes that so they don't stretch anymore.

Release note

Fixed minor UI sizing problems when attempting to share saved objects.

Screenshots before

Scenario 1

Scenario 2

Scenario 3 (using stub data, no actual aliases)

Screenshots after

Scenario 1

Scenario 2

Scenario 3 (using stub data, no actual aliases)

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: e6d2ef8
• Storybooks Preview
• Webpack Bundle Analyzer

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
spaces	152.9KB	153.0KB	+53.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[azasypkin]

JFR: Switched release_note:fix label to release_note:skip as the EUI regression that caused this issue has never been released.