Implement getInAppUrl for alerting_rule_template saved object

[MichelLosier]

Summary

Resolves: https://github.com/elastic/ingest-dev/issues/5902

• Adds implementation for getInAppUrl for the alerting_rule_template saved object. This will directly link to the rule creation form with the template values filled in.

Url route support was implemented in: https://github.com/elastic/ingest-dev/issues/5900

Screen.Recording.2025-09-18.at.9.42.18.AM.mov

Manually test

• Follow the install instructions in this PR: Add support for installing alerting_rule_template assets from packages #233533
• In the integration assets view, click the link to the template. This should send you to the rule creation form prepopulated with the template values.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• 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
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

• See some risk examples
• ...

[MichelLosier]

/ci

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 3596662

Failed CI Steps

• FTR Configs #90

Test Failures

• [job] [logs] FTR Configs #90 / Cloud Security Posture Test adding Cloud Security Posture Integrations CSPM AWS CIS_AWS Single Manual Shared Access CIS_AWS Single Manual Shared Access Workflow

Metrics [docs]

✅ unchanged

History

• 💚 Build #338506 succeeded de030e6

[jeramysoucy]

LGTM from platform security perspective - there are no changes to encrypted types

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[nchaulet]

🚀