ServiceBindingMetadata update via management interface mixes up "fixedHostName" and "fixedPort"

When a management tool uses the ProfileService management interface (as the embedded console does) to update the ServiceBindingManager service, the mapping of the received information is incorrect. The received value for a binding's "fixedHostName" property gets applied as "fixedPort" and vice versa. In most cases, both properties are "false" so this is harmless. However, if one or the other is "true" then this will lead to an incorrect binding when the server is restarted and the updated values are applied.