API: Improve representation of job's metadata `destination.table` attribute

[amotl]

About

We'd like to share an observation about suboptimal handling of schema and table names within job metadata as relayed by the Cloud API or its Croud client wrapper.

Details

It is about the destination.table attribute within the job information metadata payload: Currently, if the observation from Nov 2023 still holds true, it includes both schema and table name within an opaque string like <schema>.<table>, but the individual components are not quoted properly according to CrateDB/SQL standards, so downstream software components need to compensate.

References

• SDK and CLI for CrateDB Cloud Cluster APIs cratedb-toolkit#81 (comment)