Slave HostControllers should provide initial ignored-resource data to the master HC

When the master HC is transforming the domain-level configuration model in order to provide it to a registering slave host, it should not bother transforming resources that are going to be ignored once they arrive at the slave.

To facilitate this, the slave should include ignored-resource data as part of the "host-info" ModelNode it passes to the master when it initiates registration.

One thing this (partly) allows is registration failure on the master if it detects the presence of unignored resources that the a slave running any earlier version cannot understand. The master cannot always fail in this situation, since the slave may be configured to ignore the offending resource. Providing the ignored-resource data allows the master to make a more informed decision.

Note: I say "(partly) allows" above because the master cannot "eagerly fail" if the registering slave is running a version that precedes the completion of this task.