Incorporate Monitor Query Beta-2 UX study feedback into August (Beta-3)

[joshfree]

Tracking issue to update the August Release to incorporate the TBD Beta-2 UX Study Feedback
/cc @scottaddie

• responses must be a list in batch response , a type is unnecessary.
• avoid magic strings for aggregation and provide an enum
• aggragation param must be plural (it's a list)
• additional_worskpaces is confusing - must look into a more intuitive solution (cross language) (*) #20011
• Consider a json handler for the response.

Documentation

• the response heirarchy in metrics must be there on the readme
• Authenticate the client heading must be create the client
• In the samples, remove time generated from queries - confusing along with start_time
• Add a section on duration, start and end time, additional_workspaces
• Try using pandas on metrics for time series in samples

Action items from 7/23 meeting:

• Add an "Advanced scenarios" section to the README. Within that section, provide a link to the multi-workspace logs query code sample at https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/monitor/azure-monitor-query/samples/sample_log_query_multiple_workspaces.py.
• Add a logs query response object hierarchy tree to the README. - this will be done along with flattenning
• Add a metrics query response object hierarchy tree to the README. Update and improve README #19903
• Rename the _log_query_client.py file to _logs_query_client.py.
• "Flatten" body and tables in the logs batch query result. The goal is to make code like the following a bit simpler: #20015
  
• Add instructions to the README for locating the resource ID. Add instructions for locating the resource ID #19929

[rakshith91]

Closing - created separate issues for which there is no action item currently