But disabled when the installation is not possible because of settings
issues.

Avoiding to use the term "issues" in the title because it isn't an
accurate term. "Preflight checks" has been used instead.

To avoid "stacking contexts" problems which avoid sticky page sections
behave as expected.

Such a workaround will be not needed when migrating to latest versions
of PF6, since the problem has been addressed by droping the
DrawerContentBody from the Page component, see
patternfly/patternfly#7130 and related links

See also https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_positioned_layout/Understanding_z-index/Stacking_context

Replaced by IssuesDrawer and IssuesDrawerToggle.

Instead of doing it dinamically since the IssuesDrawer already have logic for
rendering nothing when needed. This approach helps to avoid having calls
to a query when the QueryClient has not been set yet, like at login
screen.

Which was also causing stacking problems at the selection product page.

Because it provides a benefit to the user both visually and cognitively,
as they don't have to figure out why the install button was disabled,
nor be told where to find the reasons for it.

Co-authored-by: Imobach González Sosa <[email protected]>