[Alerting] Use rule.url to generate kibanaFooterLink for email connectors

[ersin-erdal]

Resolves: #151355

This PR intends to use rule.url (provided by the rule type) in the email connector's footer link rather than the hardcoded path.

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: b8a17a5

Failed CI Steps

• FTR Configs #6

Test Failures

• [job] [logs] FTR Configs #6 / InfraOps App Logs UI Logs Source Configuration Allows indices configuration records telemetry for logs

Metrics [docs]

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	13	15	+2
securitySolution	416	420	+4
total			+6

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	14	16	+2
securitySolution	497	501	+4
total			+6

History

• 💔 Build #137083 failed 53f30cd

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

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[ymao1]

In the email connector:

kibana/x-pack/plugins/stack_connectors/server/connector_types/email/index.ts

Lines 411 to 418 in 329cc6a

	return i18n.translate('xpack.stackConnectors.email.customViewInKibanaMessage', {
	defaultMessage: 'This message was sent by Elastic. [{kibanaFooterLinkText}]({link}).',
	values: {
	kibanaFooterLinkText: kibanaFooterLink.text,
	link: `${publicBaseUrl}${kibanaFooterLink.path === '/' ? '' : kibanaFooterLink.path}`,
	},
	});
	}

it does this check link: ${publicBaseUrl}${kibanaFooterLink.path === '/' ? '' : kibanaFooterLink.path}

so should we set path to / in this error scenario?

[ersin-erdal]

Yes i saw it but "/" becomes "" anyway, and if we use it somewhere else without checking the trailing "/" the full URL becomes broken.

[ymao1]

LGTM