Introduce opamp data model for agents, starting with identity

[breedx-splk]

We need to flesh out some common data model for agents that wish to speak opamp to a server. This is the start of that. It is based on the upstream opamp spec and some additional requirements from the agent management team.

We will be following this up with additional data model and formats, like around reporting and receiving config.

[tigrannajaryan]

@breedx-splk can you make it clear that specification/opamp_datamodel.md applies to language agents only? I see some confusion from people because we read OpAMP spec section which is about Otel Collector and try to apply that section to language agents, but that's not what OpAMP spec says.

[breedx-splk]

@breedx-splk can you make it clear that specification/opamp_datamodel.md applies to language agents only? I see some confusion from people because we read OpAMP spec section which is about Otel Collector and try to apply that section to language agents, but that's not what OpAMP spec says.

Sure, I can add some clarification.

It really is frustrating that people still refer to or think of the collector as an agent.

[Kielek]

BTW any option to put this on the OpAMP/OTel specification/semantic convention?

[breedx-splk]

BTW any option to put this on the OpAMP/OTel specification/semantic convention?

Finally carved out time for this. open-telemetry/opamp-spec#310

[breedx-splk]

Note: If open-telemetry/opamp-spec#312 gets merged we will roll this back and do what upstream advises.