Fix bug where loaded event is not sent when no user ID

[joshdover]

Summary

Follow up to #102390

Fixes code that was returning early when no user ID was available. This ensures that the loaded event is still sent. Only applies to Elastic Cloud deployments where this is enabled.

[elasticmachine]

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

[TinaHeiligers]

Ideally, we should also have a test that will ensure this bug doesn't happen again. I'm not exactly sure where to add that, besides maybe trying to add one to the cloud_integration test we recently enabled?
I don't have access to the FS test account anymore and could only do a quick code review.
The bug fix itself LGTM, we can discuss adding a test as a follow up.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e3bbf07
• Storybooks Preview

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
cloud	17.1KB	17.1KB	-6.0B

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

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.14
✅	7.x

The backport PRs will be merged automatically after passing CI.

[joshdover]

Ideally, we should also have a test that will ensure this bug doesn't happen again. I'm not exactly sure where to add that, besides maybe trying to add one to the cloud_integration test we recently enabled?
I don't have access to the FS test account anymore and could only do a quick code review.
The bug fix itself LGTM, we can discuss adding a test as a follow up.

I'm actually not sure a good way to test this. There is a user event API available, but in this case we can't use it directly because we don't have a user ID to hit the API with. It's possible there's some workaround or we can try to go the mocking route which is likely easier.