Fix REST fields reported as not found and reveal more info in error log

[dmosorast]

Description of change

The error message (CRITICAL line) does not contain enough actionable info in the case where the REST API does not have a field that the discovery step finds in the WSDL.

This PR adds more information to that exception and marks the fields in the current API that cause this error as not available.

Manual QA steps

• Ran requests for each of the objects to reveal all fields
• Confirmed that with a fully selected REST catalog, at least one request per stream could be made

Risks

• Low. This is removing fields, but it seems that they either never worked or no longer work, so I don't believe this is a breaking change.

Rollback steps

• revert this branch

AI generated code

https://internal.qlik.dev/general/ways-of-working/code-reviews/#guidelines-for-ai-generated-code

• this PR has been written with the help of GitHub Copilot or another generative AI tool

[dsprayberry]

Should we consider this a minor version bump if we're removing fields?

[dmosorast]

@dsprayberry I went with a patch version bump because they return an error when requested, so this is more of a bug fix than a new feature semver-wise.

[dmosorast]

Merging because I've confirmed the relevant test now passes locally.