Support Any type in AttributeProto

[ajbalogh]

Summary

This PR adds the Any type to the AttributeProto message as a single any_val and repeated any_list.

The Any type in Any.proto is a standard Protobuf definition included with the Protobuf installation.

The rationale behind this is that a user wants to use complex protobuf messages for metrics and configuration and add them to individual et_def.Node messages.

The any_val field in AttributeProto allows a user to easily serialize/deserialize messages into a single field while preserving the structure of the message and associated internal documentation and options.

[github-actions[bot]]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

[TaekyungHeo]

Thank you for your contribution, Andy!

• Could you please share the motivation behind introducing the new fields, Any and AnyList?
• Is it necessary to import google/protobuf/any.proto? If these are not native data types supported by protobuf, could you explain the rationale for including them?

[ajbalogh]

@TaekyungHeo I've updated the summary to include the rationale behind the any type.

[srinivas212]

@ajbalogh - repeating a question @TaekyungHeo already asked... if Any is a native type, why do we need to import the type?

[ajbalogh]

@srinivas212 @TaekyungHeo - Any isn't a native type but a standard protobuf definition that is included with the protobuf installation and as result requires it to be imported.

[TaekyungHeo]

@srinivas212 , I think @ajbalogh 's point makes sense.

[tushar-krishna]

Hi @ajbalogh -- Can you try to resolve the merge conflict? We can then accept this PR to close it.