feat(#12): add otel service name as an input or env var

[pragmaticivan]

fixes #12

ref: https://github.com/open-telemetry/opentelemetry-specification/blob/f124b21de091f3d668e4ce11b954ec17e3da231f/specification/sdk-environment-variables.md#general-sdk-configuration

[nikordaris]

We need to add a test case that validates the service name. You should be able to add the the test in trace.test.ts under the "resource attributes" test suite for a test case of "has service.name resource as otelServiceName" or something like that.

[nikordaris]

Thanks for the contribution @pragmaticivan! I left a couple of comments. After those changes i think this will be good to merge in.

[pragmaticivan]

Updated @nikordaris thanks!

[pragmaticivan]

@nikordaris anything I need to fix? I just did run lint and test locally and they are all working.

[pragmaticivan]

I've just updated my node version to exactly the one used in the CI (which uses latest and will probably come with unexpected side effects).

By changing the minor version I was able to replicate it locally. Some packages are due with updates, so that might also be a good time to get it in.

[nikordaris]

@pragmaticivan ok, i think i fixed the build issues. if you pull the latest from main it should fix the build for this PR. apparently node 16.16 is stricter on version conflicts than 16.13

[ghost]

@nikordaris rebased from the main branch.

[nikordaris]

Ok the update dist action wasn't designed for forks. I need to fix that.

fixing workflow

[nikordaris]

@pragmaticivan ok i think i resolved the build issues. it looks like it created conflicts for you though. if you pull the latest, hopefully that will fix the build

[pragmaticivan]

@nikordaris rebased