Add faas instance entity

[thompson-tomo]

Changes

Enable instance to be able to be an entity which required rename of the attribute.

By having instance as an entity we are following the pattern in other namespaces, we can have the faas entity describing the function whereas the instance describes an instance of when said function has been run.

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• Links to the prototypes or existing instrumentations (when adding or changing conventions)

[tylerbenson]

I don't have any problems with this change. We asked the author to implement this in one of the languages for review purposes and be prepared to implement it in a couple other languages if it's approved.

[thompson-tomo]

@tylerbenson thanks for feedback, see open-telemetry/opentelemetry-dotnet-contrib#3087 for the update done to the dotnet implementation. Key thing being scope is naming update rather new attributes.

I would suggest looking to stabilise or atleast moving to beta/rc stability for atleast the function & instance namespaces that implementations can be updated in bulk.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[joaopgrassi]

I will close this PR as there's no current SIG active for FaaS and no clear code owners to review/work on a migration path for this.