[SNOW-3203938] Fix ai_parse_document_basic test

[sfc-gh-mrek]

1. Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes SNOW-3203938

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
     • If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing
   • I am adding new logging messages
   • I am adding a new telemetry message
   • I am adding new credentials
   • I am adding a new dependency
   • If this is a new feature/behavior, I'm adding the Local Testing parity changes.
   • I acknowledge that I have ensured my changes to be thread-safe. Follow the link for more information: Thread-safe Developer Guidelines
   • If adding any arguments to public Snowpark APIs or creating new public Snowpark APIs, I acknowledge that I have ensured my changes include AST support. Follow the link for more information: AST Support Guidelines

3. Please describe how your code solves the related issue.

With latest changes related to the new error handling, basic parse document tests started failing because metadata key is mising in the response.
This is expected behaviour, more details can be found here.
I've modified tests to use session parameter, to test both legacy and new response without error details (the bcr process lasts ~3 months, so during this time both combinations will be available for clients).
It affects ai_parse_document only, as for other functions the value didn't change.
New response type is {value:, error}, but when response error details are disabled, value is extracted.
In case of ai_parse_document, metadata was moved to the root level of the response {value,metadata,error} making it absent in value.
As a follow-up, it would be a good idea to cover new error handling with error details in these tests.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[sfc-gh-mrek]

I have read the CLA Document and I hereby sign the CLA

[sfc-gh-aling]

we normally do not do this because our tests run in parallel and it might pollute other test

[sfc-gh-mrek]

So how can I control the behaviour based on the parameter?
For a bit we'll live in a world where user can have AI_SQL_ERROR_HANDLING_USE_FAIL_ON_ERROR either enabled or disabled. It changes the response format for the default ai_parse_document behavior (as i explained in linked doc, the metadata is moved out of the value object for AI_SQL_ERROR_HANDLING_USE_FAIL_ON_ERROR=false).
Also, as this parameter is currently opt in, based on the account cofiguration tests will either succeed or fail if we leave the metadata check.

Should there be an assumption that moving forward metadata won't be at top level so the check should be simply removed (even though for some accounts it can still be here?).
This doesn't look like a good change, but at the same time is the safest one if we can't use session params to fully control functions behavior :)