refactor(instrumentation-http): migrate away from getEnv()

[pichlermarc]

Which problem is this PR solving?

Migrates away from getEnv() to the new functions and inline-defaults introduced in #5443. Since the HTTP instrumentation can only be used on Node.js, everything stays as-is for the end-user. This is a pure refactor.

Refs #5217

Type of change

• refactor

How Has This Been Tested?

• Existing tests

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.93%. Comparing base (5b988c8) to head (89fd849).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5469   +/-   ##
=======================================
  Coverage   94.93%   94.93%           
=======================================
  Files         309      309           
  Lines        8002     8002           
  Branches     1686     1686           
=======================================
  Hits         7597     7597           
  Misses        405      405           

[trentm]

Sometimes prettier is trolling.

[david-luna]

I wonder if we should use a lint rule for this. Probably is difficult because sometimes the import order matters and is not just code style.

[pichlermarc]

I think a lint rule could be helpful. 👍 I don't think there's a case where we'd split importing from the same package, most of the time when import order matters it's from different packages, so we'd do:

import {a} from 'my-package';
// doing some stuff
import {b} from 'other-package';

but not

import {a} from 'my-package';
// doing some stuff
import {b} from 'my-package';