Search Parameter validation failure issues logged

[rajithaalurims]

Description

This PR is about logging the actual reason that caused Search Parameter validation failure and logs InvalidDefinitionException in Exception Telemetry for different accounts in search parameter definition builder.

Current code captures details about what is causing validation failure but not logging it. I modified code to log the cause that fails validation.

Related issues

Addresses [issue # 88668].

Testing

Do not have invalid search parameters in my local or Test.
So tested it by breaking the code intentionally to confirm detailed logs are showing up.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

[fhibf]

Maybe we can simplify this part of the code with:

catch (FhirException ex)
{
    StringBuilder issueDetails = new StringBuilder();
    foreach (OperationOutcomeIssue issue in ex.Issues)
    {
        issueDetails.Append(issue.Diagnostics).Append("; ");
    }
    
    _logger.LogWarning(ex, "Error loading search parameter {Url} from data store. Issues: {Issues}", searchParam.GetStringScalar("url"), issueDetails.ToString());
}

[fhibf]

As InvalidDefinitionException and SearchParameterNotSupportedException inherit from FhirException, a single catch block can simplify the code.