feat(opencensus-shim): add OpenCensus shim package boilerplate

[aabmass]

Which problem is this PR solving?

Part of #3749 with more PRs to follow. Next PR draft #3751

Short description of the changes

Adds the boilerplate for opencensus shim package.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

This contains no actual code, but npm lint passes.

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated
  I'm planning to add a changelog entry in the final PR of the set where this is actually fully implemented.

[codecov]

Codecov Report

Merging #3750 (f783898) into main (cd0d880) will increase coverage by 0.00%.
The diff coverage is n/a.

❗ Current head f783898 differs from pull request most recent head 89af775. Consider uploading reports for the commit 89af775 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3750   +/-   ##
=======================================
  Coverage   93.43%   93.44%           
=======================================
  Files         290      289    -1     
  Lines        8849     8829   -20     
  Branches     1834     1829    -5     
=======================================
- Hits         8268     8250   -18     
+ Misses        581      579    -2     

see 2 files with indirect coverage changes

[pichlermarc]

Thank you for adding this. 🙂
Looks like this will need a changelog entry, and then this PR should be good to merge 🙂

[aabmass]

@pichlermarc should I add a changelog entry for each PR in the series or just one entry once it's in a usable releasable state?

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: aabmass / name: Aaron Abbott (992a052, 8a31f08, 62ae7d0)

[pichlermarc]

@pichlermarc should I add a changelog entry for each PR in the series or just one entry once it's in a usable releasable state?

@aabmass I think previously, we've had each PR for a new package have its own changelog entry, even if just adding boilerplate code, so we'd prefer this approach 🙂

[pichlermarc]

/easycla

[dyladan]

@pichlermarc should I add a changelog entry for each PR in the series or just one entry once it's in a usable releasable state?

@aabmass I think previously, we've had each PR for a new package have its own changelog entry, even if just adding boilerplate code, so we'd prefer this approach 🙂

I actually think we should try to make our changelogs more user focused. @pichlermarc is right in the past we've done one per PR but I think having a single changelog entry for the release is friendlier to users.

[pichlermarc]

@pichlermarc should I add a changelog entry for each PR in the series or just one entry once it's in a usable releasable state?

@aabmass I think previously, we've had each PR for a new package have its own changelog entry, even if just adding boilerplate code, so we'd prefer this approach slightly_smiling_face

I actually think we should try to make our changelogs more user focused. @pichlermarc is right in the past we've done one per PR but I think having a single changelog entry for the release is friendlier to users.

Makes sense. In that case I'll apply the skip-changelog label as we've set the package to private now, then we can add a changelog entry when we set private to false . 🙂

[aabmass]

The failed window test looks like a flake, can someone re-run the failure? bumped and its passing