Replace option for navigateToApp

[flash1293]

Currently core.application.navigateToApp is always writing a new history entry for doing a navigation (

kibana/src/core/public/application/application_service.tsx

Line 131 in a091124

this.history ? this.history.push(url, state) : redirectTo(basePath.prepend(url));

).

In some cases when no history entry should be written, a replace option should be available.

One use case for this is redirecting legacy routes - in that case producing a history entry will cause the browser back button to break because it will just lead to the redirected route again.

cc @restrry

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[pgayvallet]

One use case for this is redirecting legacy routes

By legacy route, you means route to a legacy plugin? Because when navigating from and/or to a legacy app, we are not using the history and just performing a plain window.location.assign instead.

kibana/src/core/public/application/application_service.tsx

Lines 115 to 117 in a091124

	redirectTo = (path: string) => {
	window.location.assign(path);
	},

So we would need to handle both cases when implementing replace, correct?

[flash1293]

@pgayvallet

By legacy route, you means route to a legacy plugin?

That was badly worded by me - legacy route doesn't mean legacy plugin necessarily. Just in general when a route has moved and requests to the old one should be redirected to the new one.

For my use case it's not necessary to support legacy routing.

[pgayvallet]

Blocker for #68284 that needs to lands in 7.9.