[Fleet] Render extension component after initializing package policy

[orouz]

Summary

extracted from #149137 (comment):

sometimes validationErrors and packagePolicy goes out of sync:

this happens when our extension component fires an effect on mount to initialize the package policy before fleet's effect (init())

making this property stateful makes the extension component render only after fleet's effect has fired, which sorts out the ordering.

still kinda odd they are not in sync tho, even if fleet's effect fires last, i'd expect the policy to be changed as well. you can check the logs and reproduce this on env by going to the install page -> canceling and going in again

@nchaulet

Checklist

Delete any items that are not applicable to this PR.

• 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
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[nchaulet]

LGTM! thanks for fixing that

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 1576af5

Failed CI Steps

• FTR Configs #41
• FTR Configs #42

Test Failures

• [job] [logs] FTR Configs #41 / Alerting eventLog alerts should generate expected alert events for normal operation
• [job] [logs] FTR Configs #42 / Reporting APIs Usage Usage Counters API counters: management job info

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
fleet	925.4KB	925.5KB	+29.0B

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