Update proto

[dyladan]

Upgrade the version of the proto in the various OTLP exporters to support latest features

• Move proto to a shared location if possible
• Use autogenerated JS from the proto repo if possible

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[dyladan]

not stale

[dyladan]

@pichlermarc this is done now right?

[pichlermarc]

Yes this is done (according to the title) 🙂

However:

• Move proto to a shared location if possible
  • is not done: currently there are two proto locations (down from 4 locations previously)
• Use autogenerated JS from the proto repo if possible
  • is not done AFAIK: we do not use autogenerated JS, or at least it is not documented that we do.

[pichlermarc]

Also there has been another release since #2929 merged.

[dyladan]

• Move proto to a shared location if possible

  • is not done: currently there are two proto locations (down from 4 locations previously)

This should probably be a separate issue if we're going to handle it.

• Use autogenerated JS from the proto repo if possible

  • is not done AFAIK: we do not use autogenerated JS, or at least it is not documented that we do.

This is definitely not done and was a specific choice because the autogenerated code was difficult to package the way we wanted to keep bundles small. We can create a separate issue for this if it is something we want to try again in the future, but it will be tough to do in a non-breaking way after metrics is GA I think