Preserve originId when overwriting existing objects

[jportner]

Related to #135346 (partially resolves this issue).

Overview

If an existing object is being overwritten (via create/bulkCreate), Kibana now preserves its originId field if it has one. This behavior can be overridden by specifying originId: undefined.

I also added validation to ensure that originId is only set for multi-namespace object types (it would basically have no effect for single-namespace object types, but we shouldn't allow it).

Testing

1. Start Kibana
2. Add sample data
3. Create "Another" space
4. Copy a dashboard to Another space using the "Check for existing objects" option
5. In Another space, make a change to the dashboard and save it
6. In the Default space, copy the dashboard again using the "Check for existing objects" option
7. Observe that there are is still only one copy of the dashboard in Another space, and you can examine it to verify it still has the originId field

Additional info

This does not attempt to "repair" any saved objects that have had their originId field cleared out, it can be done in a separate PR, see the linked issue for more details.

[elasticmachine]

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

[TinaHeiligers]

I'm not sure why FTR configs are failing but changes LGTM as a partial fix.

[lukeelmers]

LGTM, thanks for jumping on this so quickly ❤️

[jportner]

I'm not sure why FTR configs are failing but changes LGTM as a partial fix.

This PR adds validation to prevent consumers from setting the originId field unless the object is share-capable or shareable (e.g., "multi-namespace").

The importSavedObjects module gives consumers the option to create new copies of objects with random IDs, and that blindly sets originId: undefined for all objects that are being imported. So I had to change that case to omit the originId field entirely instead of just setting it to undefined.

[kibana-ci]

💚 Build Succeeded

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

Metrics [docs]

✅ unchanged

History

• 💔 Build #54065 failed 8e8fe84
• 💔 Build #54028 failed ba4ca89

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

[bataya0]

@geekpete I think this is relevant to the work your doing.