Make URL link domain/site metadata resolution more resilient

Problem/Motivation

Often a site can be accessed from a number of domains.
There is a risk that the site (sent as meta-data in FlightManifest) might not match the link domain (set in hal.settings.yml and sent in encrypted content).
In this case the incoming entity type/bundle resolution fails and you get a message like

The entity of type http://{hal.settings.link_domain}/rest/type/user/user cannot be imported by this site and was ignored.

In most cases this could be misconfiguration of link domain in hal settings or an issue with not passing the correct --url or -l flag to drush.

Proposed resolution

Possible approaches

• Use the hal link domain universally?
• Support making the domain in the metadata configurable, in the arrival

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet