Fix http-instrumentation-pyroscope not using name tag

[mstoykov]

Description

the name tag was not accessed properly

Fix found by @andrewslotin

Please fill in this template.

• Use a meaningful title for the Pull Request. Include the name of the jslib added/modified.
• Fill the description section of the Pull Request.
• Test the change in your code, and ensure the npm run test command succeeds.
• Run yarn run generate-homepage locally and verify the new homepage /lib/index.html file looks legit.

Select one of these and delete the others:

If publishing a new version of an existing jslib:

• The Pull Request is labeled with the version bump label.
• The Pull Request adds a /lib/{jslib_name}/{desired_version} folder.
• The Pull Request adds a /lib/{jslib_name}/{desired_version}/index.js file containing the jslib's code bundle.
• The Pull Request updates the supported.json file to contain an entry for the newly added jslib version, as in the following example:

{
  "my-lib": [
    "1.0.2",
    // Use semantic versioning
    "{desired_version}"
  ]
}

• The Pull Request adds the relevant tests to the /tests/basic.js and /tests/testSuite.js files to ensure that the new version of the jslib is importable and runnable by k6.
• Merge the Pull Request once it is green. PRs adding new jslib versions do not require to get a review to be merged 🚀.

[andrewslotin]

❤️

[mstoykov]

Technically we are supposed to bump the version and release a new one.

I am not certain it is worth it though, unfortunately I am also not certain that the caching will be update correctly too :(

[andrewslotin]

@mstoykov, let's bump the patch version to avoid any possible caching issues.