[Azure.Core] Add Public Model Serialization

[nisha-bhatia]

Add Public Model Serialization classes to all Models
To be completed by May Milestone

Checklist:

• Add SerializableOptions as a parameter to IUtf8JsonSerializable

• azure-sdk-for-net/sdk/metricsadvisor/Azure.AI.MetricsAdvisor/src/Utf8JsonWriterExtensions.cs

  Line 18 in 652dc91

  public static void WriteNullObjectValue(this Utf8JsonWriter writer, string propertyName, object value)

  needs case for ISerializable

Fixes:

• Deserialize AnalyzeResult [FEATURE REQ] #37094
• [FEATURE REQ] Expose DeserializeGenericResourceData  #35783
• Text Analytics: Consider Supporting Operation Result Serialization  #28358
• [BUG] Azure.ETagConverter is internal, blocks using System.Text.Json source gen to deserialize objects #35201 (comment)
• [QUERY] How to deserialize OpenAI ChatMessage correctly? #35963
• TypeSpec: .NET JSON serialization/deserialization for enums -- add generation of a custom converter? autorest.csharp#3353
• [BUG] Support complex types in Azure Monitor Query results #37475

[nisha-bhatia]

#35783

[nisha-bhatia]

#28358

[nisha-bhatia]

#35201 (comment)

[nisha-bhatia]

#35963

[nisha-bhatia]

Azure/autorest.csharp#3353

[jsquire]

Duplicate: #38763

[weng5e]

Thanks for pointing to this tracking work item from the duplicated issues. It seems like the mile stone has been changed several times. Is this work item commited? Could you please also share an very rough ETA for this work item?

[jsquire]

The only statement that I can make is that this is something that we are working on. There is no committed timeline that I can share.

[jsquire]

Duplicate: #39107.

[BlackGad]

Could you include clone methods? In our use cases, we need to adjust request options just before dispatching them. Modifying properties of the original instance is not convenient operation :)

[annelo-msft]

@m-nash, I believe the work on the Core side of this is complete with the release of System.ClientModel v1.0.0. If work remains to implement model serialization in various client libraries, should this be moved to track those separately?

[stevendarby]

Find the tracking of this work very hard to follow.

Items raised for specific models are closed as duplicates, referring to this item, e.g. #38763 (comment)

But comment above suggests the core work is done and individual clients/models may need to add support, so should some of those "duplicates" be re-opened?

Also the issue lists several issues which it is supposed to fix when done, but some of those are already closed, leaving the current state of this work unclear.

Personally I'm interested the status of AnalyzeResult.