opentelemetry: fix import ordering

[danberdev]

Just an import ordering fix
Also one ignore for mypy due to untyped auto_instrumentation (ugh!)

[vrslev]

LGTM, давай ещё исправим CI?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Flag	Coverage Δ
unittests	98.85% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
microbootstrap/bootstrappers/fastapi.py	100.00% <100.00%> (ø)
...obootstrap/instruments/opentelemetry_instrument.py	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[danberdev]

@vrslev fixed all issues, also fixed one test that you've added, please take a look, thanks!

[vrslev]

All good, do we need to test the actual auto instrumentation? or is it too hard?

[danberdev]

All good, do we need to test the actual auto instrumentation? or is it too hard?

I think it's pointless due to these reasons:

1. It's an obscure magic method from opentelemetry with unpredictable side-effects. (Honestly, I don't like it, I'd better stick with explicit initializations, but in the end of the day no code is better than a little code)
2. Auto instrumentation behavior depends on installed instruments
3. We have some tests on installed instrumentation (Pyroscope e.g.)
4. Yeah, it's really hard in the end of the day. I can think of some possible ways (and considering obscure magic method it might be even desirable in case of changes in opentelemetry), but it would take considerable time and effort to engineer that, I'd keep it as a good task for later.