Publish values on close in OTLP registry

[jonatan-ivanov]

The fix for partial publish on close was not applied to OTLP registry.

Closes gh-3773
See gh-1882

[jonatan-ivanov]

@lenin-jaganathan If you are up to and have some time, would you mind taking a look at this?

[lenin-jaganathan]

@jonatan-ivanov Linking to my comment on the other PR which tries to fix rollover at the top of the minute - #3794 (comment)

It seems this also falls in the same bag of somehow duplicating things from StepRegistry but we can't inherit OTLPRegistry from step registry as it is not just a StepRegistry. Just thinking if we could combine these two PRs and come-up with something better with lesser duplications. cc: @shakuzen

[jonatan-ivanov]

@lenin-jaganathan This PR is a little more problematic than yours but since we started the discussion there, see my answer there: #3794 (comment)

[lenin-jaganathan]

Now that StepTuple2 has been copied over to OTLP. I guess can this support StepN, which can hold count, total, and max, (maybe step-histogram too) so that it makes sure that complete rotation of StepMeter happens with minimal overhead.
Do you think will it be hard to have StepHolder which can hold 'N' items aligned to the same step and should be rotated together?

[jonatan-ivanov]

The concern I have is instead of poll1 and poll2 there should be a poll(index) as well as you should provide a collection of "noValue" and a collection of Supplier.
I think this can be chaotic rather quickly.

I would like to look into improving step-histogram and max (we don't have an interface for that), so that we can make things simpler and more robust. Once we are there, this idea can be handy but right now I think I would prefer separate types.