Warning statement should be issued when an explicitly-configured search parameter doesn't exist

[sfc42]

Describe the bug
Warning statement should be issued when an explicitly-configured search parameter doesn't exist

Environment
4.11.0

To Reproduce
Steps to reproduce the behavior:

1. Add a search parameter to the server-config file that doesn't exist
2. The server starts, but doesn't warn the user the search parameter doesn't exist.

Expected behavior
A warning should end up in the log to tell the user the search parameter doesn't exist.

Additional context
Add any other context about the problem here.

[sfc42]

The pull request for this issue was merged: #3221

[kmbarton423]

Confirmed new warning message received on startup when a non-existent search parameter is specified in fhirServer/resources//searchParameters:

ParametersUti W Search parameter 'favorite-food' with the configured url 'http://ibm.com/fhir/SearchParameter/Patient-favorite-food' for resourceType 'Patient' could not be found.

[kmbarton423]

Also confirmed new warning message received on startup when a non-existent search parameter is specified in fhirServer/resources/Resource/searchParameters:

ParametersUti W Search parameter 'favorite-food' with the configured url 'http://ibm.com/fhir/SearchParameter/Patient-favorite-food' for resourceType 'Resource' could not be found.