Support legacy inflection behavior

When receiving an inflection request (i.e. request ending in ?, ??, or ?info, the legacy N2T service would either return metadata or redirect to the target for metadata. The current implementation always returns metadata for such a request. This behavior is desirable for technical evaluation of the request, but does not provide the same experience for non-technical users.

Task here is to support redirection to the registered target for an inflection request, but still provide information about the registration when needed.

The approach taken will be to compare the requested identifier string with the registered information. If there is an exact match, then the resolver should return information about the identifier registration. If there is any suffix portion (i.e. the supplied identifier is not an exact match to the registered information), the client should be redirected to the target along with the same inflection request parameters.