WFLY-2527 Don't require a generic (foo=*) ManagementResourceRegistration to execute wildcard ops

The read-resource-description op supports wildcard results (with the result being a list with one element per match) but this fails if the target resource type does not have a generic MRR registered. This patch fixes that.

The last commit also makes read-operation-description more lenient when the user specifies a wildcard address but there is no wildcard registration. The OSH now checks if all registered non-wildcard MRRs have the op and with the same description and flags; if so that description/flags are used to prepare the response.

The more lenient read-operation-description behavior is necessary to make the read-resource-description fix useful in the CLI. Without it the CLI's background validation of the user's read-resource-description input will fail. The validation uses read-operation-description.