Restore error message changes for bad conditional references

[lmsurpre]

Describe the bug
In 4.9.2 we shipped changes for #2556 so that we get important diagnostic info from bundles with bad conditional references.

Unfortunately, we seem to have lost those edits as part of a large bundle processing refactor on main.

Environment
Which version of IBM FHIR Server?

To Reproduce
Steps to reproduce the behavior:

1. submit a transaction bundle with conditional references that have 0 or >1 match.

Expected behavior
The response should contain an OperationOutcome.Issue that details:

1. the value of offending conditional reference (i.e. the query that we barfed on)--probably in the description
2. the location of the field with this conditional reference (at the very least the Bundle entry's index)--probably in the "expression"

Additional context
See #2772 for what we did for this the last time.

[kmbarton423]

Confirmed issues created for conditional references in a transaction bundle for the following cases:

• reference does not resolve
• reference resolves to multiple
• reference search is invalid

in all cases the resulting issue contains an expression indicating the location (Bundle.entry[x])
confirmed varied location of failure within the bundle were represented accurately