fix: add Hapi and Koa to default supported plugins

[carolinee21]

Short description of the changes:

• Adds references to Hapi and Koa plugins in list of default supported plugins

[codecov]

Codecov Report

Merging #1440 into master will decrease coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1440      +/-   ##
==========================================
- Coverage   93.89%   93.79%   -0.11%     
==========================================
  Files         148      144       -4     
  Lines        4393     4079     -314     
  Branches      894      847      -47     
==========================================
- Hits         4125     3826     -299     
+ Misses        268      253      -15     

Impacted Files	Coverage Δ
packages/opentelemetry-node/src/config.ts	100.00% <ø> (ø)
...telemetry-plugin-fetch/src/enums/AttributeNames.ts
...ry-plugin-xml-http-request/src/enums/EventNames.ts
packages/opentelemetry-plugin-fetch/src/fetch.ts
...s/opentelemetry-plugin-xml-http-request/src/xhr.ts

[dyladan]

Please add them to the plugins-node-all metapackage also.

[dyladan]

Can you also add them to the metapackage?

[carolinee21]

Can you also add them to the metapackage?

Yes sorry just added!

[carolinee21]

Seems like the metapackage is currently failing to build because "'@opentelemetry/[email protected]' is not in the npm registry."
Should I wait for this to be published, or is there a better way to handle linking to an internal package?

[obecny]

Seems like the metapackage is currently failing to build because "'@opentelemetry/[email protected]' is not in the npm registry."
Should I wait for this to be published, or is there a better way to handle linking to an internal package?

I would rather block adding anything more to plugins-node-all until it will be moved to contrib repo due to the problems we already had with different version in a node_modules (sdk package), @dyladan WDYT ?

[dyladan]

Seems like the metapackage is currently failing to build because "'@opentelemetry/[email protected]' is not in the npm registry."
Should I wait for this to be published, or is there a better way to handle linking to an internal package?

I would rather block adding anything more to plugins-node-all until it will be moved to contrib repo due to the problems we already had with different version in a node_modules (sdk package), @dyladan WDYT ?

Sure :)

[dyladan]

@carolinee21 sorry to give you the runaround but can you remove the metapackage change for now?

[carolinee21]

@carolinee21 sorry to give you the runaround but can you remove the metapackage change for now?

Yep, just did! Thanks