refactor: unifying shutdown once with BindOnceFuture

[legendecas]

Which problem is this PR solving?

The procedure of shutdown once is implemented at several places. It may be good to have them all to share an abstract BindOnce structure.

Type of change

• New feature (non-breaking change which adds functionality)

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated

[codecov]

Codecov Report

Merging #2695 (2bb3a6e) into main (5f3cbc2) will increase coverage by 0.25%.
The diff coverage is 97.01%.

@@            Coverage Diff             @@
##             main    #2695      +/-   ##
==========================================
+ Coverage   92.57%   92.82%   +0.25%     
==========================================
  Files         151      153       +2     
  Lines        5277     5267      -10     
  Branches     1116     1112       -4     
==========================================
+ Hits         4885     4889       +4     
+ Misses        392      378      -14     

Impacted Files	Coverage Δ
...ckages/opentelemetry-exporter-jaeger/src/jaeger.ts	94.59% <90.90%> (+3.68%)	⬆️
...dk-trace-base/src/export/BatchSpanProcessorBase.ts	94.38% <92.30%> (+2.80%)	⬆️
...s/exporter-trace-otlp-http/src/OTLPExporterBase.ts	100.00% <100.00%> (+7.84%)	⬆️
packages/opentelemetry-core/src/utils/callback.ts	100.00% <100.00%> (ø)
packages/opentelemetry-core/src/utils/promise.ts	100.00% <100.00%> (ø)
...y-sdk-trace-base/src/export/SimpleSpanProcessor.ts	91.30% <100.00%> (+7.43%)	⬆️

[pichlermarc]

Looks good! This will definitely be useful in other places as well. 💯

[Flarna]

Added breaking label late here. It's breaking because protected _isShutdown: boolean = false; was removed resulting in build errors like this (see e.g. #2788).

Error: packages/exporter-trace-otlp-grpc/src/OTLPExporterNodeBase.ts(78,10): error TS2339: Property '_isShutdown' does not exist on type 'OTLPExporterNodeBase<ExportItem, ServiceRequest>'.

Actually not that an issue as it happened before 1.x was made.

[legendecas]

@Flarna we can add the flag back. Didn't notice it is a protected property rather than a private property.

[Flarna]

@legendecas That was not my intention here. It's just about getting it correct into the next release notes/changelog. It happens before 1.x as released so the perfect timing.
In the past we mentioned breaking changes in the readme but not sure if this is still the case.