Use execution context for Fullstory

[lizozom]

Summary

Depends on #126777

• Uses the new information from our execution context (app name, page name, entity id) and passes it to Fullstory.
• Replaces the use of setUserVars with setVars which matches our type of data better.
• Fixes an integration bug where users are not scoped to their organization, causing all users with the same name to be counted as a single user.
• Pass the Elastic organization id to fullstory

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

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[lizozom]

@elasticmachine merge upstream

[lizozom]

@elasticmachine merge upstream

[afharo]

LGTM! Just added 1 nit for providing the org_id_str as part of the identify call if possible.

[kibana-ci]

💚 Build Succeeded

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

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
cloud	8.6KB	8.8KB	+256.0B

History

• 💚 Build #27880 succeeded b4899ec
• 💔 Build #27876 failed 86f8820
• 💚 Build #27867 succeeded 7b3d03d
• 💚 Build #27850 succeeded 5cb2b97
• 💚 Build #27388 succeeded adea846

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

cc @lizozom

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.1

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

Questions ?

Please refer to the Backport tool documentation