add sentry-conventions to auto-approve

[lcian]

This is an internal package and teams other than SDKs will want to release it.

[BYK]

Can you please provide more information about why we need auto publishing for this? It looks like this is publishing to npm and PyPI and it's not very clear what the repo is or why were publishing to those places for me to do a risk assessment.

[lcian]

This package contains the Sentry semantic conventions for things like span attributes.
Right now we publish to pypi and npm, and this is used in sentry and snuba and as a git dependency in realy.
In the future we're going to start using these packages in the SDKs and publish to more places as we begin to generate code for more platforms.

The reason to set it to auto-publish is that a product team that's in US timezone might want to release this to use a new/updated attribute, and they would need to wait until someone from the SDKs team approves the release (as we're the only ones that have the rights on this I think).

I guess there might be some valid concerns as this is something that will eventually get shipped to customers in the SDKs.
So maybe we can just keep this not on auto publish or we can find a different way.

[BYK]

@lcian approvals are not limited to SDK teams so we can talk about that instead of auto approve. Is that okay?

[BYK]

Closing due to inactivity.