We return SUCCESS_HIL_OK when invalid remanent data is set

When remanent data was set by the host application (tag host responsibility set to "remanent data stored by host"), SUCCESS_HIL_OK was always returned even if bad data was set (inconsistent, invalid length). This has been fixed and appropriate error codes will now be returned.

Regardless of the error code, the packet will always be accepted as a state transition to "remanent data was set by the host application" by the protocol stack, as long as the packet specifies at least the valid component ID.