[SavedObjects] Adds FTR test for identifying failed validation when supporting attribute re-writing for sort

[spong]

Summary

This is a follow-up to #114585 that adds an FTR test for exercising a nested agg specifying a sort field from the root object as requested here.

See this issue for more details: #115153.

Please let me know if I misunderstood the requested test scenario here, and/or if a specific validation unit-test would be helpful here as well -- thanks! 🙂

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

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

[banderror]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 06d46c4
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💛 Build #1160 was flaky 222cab3

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

cc @spong

[pgayvallet]

Sorry if I wasn't clear. In https://github.com/elastic/kibana/pull/114585/files#r729620927 I was just asking that your feature using top_hits.sort was properly covered by FTR/integration tests so we detect a potential failure when we'll perform the path rewriting by addressing #115153

[spong]

Sorry if I wasn't clear. In https://github.com/elastic/kibana/pull/114585/files#r729620927 I was just asking that your feature using top_hits.sort was properly covered by FTR/integration tests so we detect a potential failure when we'll perform the path rewriting by addressing #115153

Thanks for the clarification! In that case we're good here 🙂 -- I've verified we've got existing FTR/integration tests (find_statues/find_rules) that will fail once #115153 is resolved, so going to go ahead and close out this PR. I also added a note here as the to necessary changes within security security, and will comment on the issue as well. Thanks @pgayvallet!