This is a followup to #1302:

Right now there's some special handling of named pages, but instead we'd like to put "named page" into other phrases. For instance open [name:pageName] that would match named pages.

To do this we need a new page type (in entityTypes.js) that is dynamically filled with the available names. This would also mean that page names would respect aliases and ignore stopwords.

I believe textMatching.Alternatives can accept a mutable array, and if that array is changed then the pattern matching will change. So we can instantiate the alternatives, and modify it when storage is initialized and as commands are executed that change the named pages. Ideally this would happen in the functions suggested by #1483