Add compatibility with core path_alias module

Problem/Motivation

I would like to create a path alias (eg. /foo) for a views pretty path (eg. /view/filter/type/foo).

Currently when I visit the aliased path, none of the filtering is applied (I get the unfiltered view page).

I'm also finding that the Redirect module → 's send-everything-to-the-aliased-path functionality is similarly not working here (if I visit the unaliased path I am not redirected to the aliased one). I suspect this is related.

Steps to reproduce

1. Create a path alias (eg. /foo) for a views pretty path (eg. /view/filter/type/foo).
2. Visit the path alias (eg. /foo).
3. See that the views pretty path filters (eg. /filter/type/foo) are not applied.

Proposed resolution

TBD. Analysis of how the Facets Pretty Paths module → achieves a similar goal may produce fruit here as that module is fully compatible with both core path aliases and Redirect module functionality.

Remaining tasks

Propose resolution, open MR, pass review & testing.

User interface changes

None.

API changes

TBD.

Data model changes

TBD.