Notifications API: remove hard-coded dataset urls from message text #11648
Description
In the Notifications API, the message text sometimes contains a hard-coded reference to the JSF Dataset page. This needs to be more dynamic so that it can be used by the SPA, or other clients that don't use the JSF frontend.
For example, here are some notifications currently defined in the bundle.properties:
notification.ingestCompleted=Dataset <a href="/dataset.xhtml?persistentId={0}" title="{1}">{1}</a> has one or more tabular files that completed the <a href="{2}/{3}/user/dataset-management.html#tabular-data-files" title="Tabular Data Files - Dataverse User Guide" target="_blank" rel="noopener">tabular ingest process</a> and are available in archival formats.
notification.ingestCompletedWithErrors=Dataset <a href="/dataset.xhtml?persistentId={0}" title="{1}">{1}</a> has one or more tabular files that are available but are not supported for <a href="{2}/{3}/user/dataset-management.html#tabular-data-files" title="Tabular Data Files- Dataverse User Guide" target="_blank" rel="noopener">tabular ingest</a>.
As a temporary solution while both JSF and SPA UIs are deployed, an extra parameter can be defined on the endpoint, a flag that specifies that all links within the messages should be SPA links. By default, the JSF links can be returned.