Clarify the HTTP client http.retry_count spec

[mateuszrzeszutek]

Fixes #2737

Changes

Clarifies when the http.retry_count attribute should be added to the HTTP client span (every time the HTTP request gets re-sent, no matter what the cause is).

I also added a grouping "Examples" header for all examples, similar to other (messaging, DB) convention docs.

[joaopgrassi]

Thanks for the extra examples and for better formatting them :)

I just have a question on naming. The attribute is retry but in the text we use the word re-send/sent. Not sure if it's a problem but I wonder if we shouldn't be consistent?

[mateuszrzeszutek]

I just have a question on naming. The attribute is retry but in the text we use the word re-send/sent. Not sure if it's a problem but I wonder if we shouldn't be consistent?

I'm in favor of this idea; initially I didn't want to change too much of the spec, just clarify things, but if more people than just me think it's a valid point I think we could rename it to resend_count.
(I also mentioned this in #2743 (comment))

[github-actions]

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

[mateuszrzeszutek]

@open-telemetry/specs-approvers @open-telemetry/technical-committee please take a look at this PR

cc @lmolkova (sorry, I completely forgot to tag you before 🙈)

[lmolkova]

LGTM, thank you @mateuszrzeszutek!

[joaopgrassi]

Sorry, forgot to hit send in one comment: You probably need to add an entry to the changelog for this as well, otherwise looks good to me.

[github-actions]

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

[trask]

/unstale

[reyang]

LGTM.

[github-actions]

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

[mateuszrzeszutek]

Ping @open-telemetry/technical-committee : is this PR ready to be merged? Is there anything else that I can help with?