Close Reader in JsonInputFunctions

[tejasae-afk]

This in JsonInputFunctions only surfaces in the edge case, so may not be a priority. The resource opened there can leak if JsonInputFunctions exits on an error path. this patch moves the allocation into try-with-resources so cleanup happens on every exit path.

Happy to revise the approach or close this if it doesn’t fit — you know the codebase far better than I do.

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[github-actions]

This pull request has gone a while without any activity. Ask for help on #core-dev on Trino slack.

[martint]

Thanks @tejasae-afk. There's no resource leak in this case. The reader is an ephemeral view over an in-memory byte sequence (Slice).