Ensure nodejs path globs prepend all relative path strings with ./

[rquitales]

Proposed changes

The latest version of the NodeJS glob package introduced in #2858 has slightly different behaviour than in the previously used version. This PR sets the options for these glob functions to maintain backwards compatibility and ensure our resource urns do not change.

Related issues (optional)

Fixes: #2860

[github-actions]

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 25.46%. Comparing base (e74728b) to head (fd7e8e7).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2861   +/-   ##
=======================================
  Coverage   25.46%   25.46%           
=======================================
  Files          48       48           
  Lines        7532     7532           
=======================================
  Hits         1918     1918           
  Misses       5456     5456           
  Partials      158      158           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mjeffryes]

Thanks for tracing this down! (Does this test not run on PRs? Curious why we didn't see the failure before merge.)

How confident do you feel that this is the only behavior change from the new version of glob? Do we need to do more sanity checking before release?

[rquitales]

Thanks for tracing this down! (Does this test not run on PRs? Curious why we didn't see the failure before merge.)

How confident do you feel that this is the only behavior change from the new version of glob? Do we need to do more sanity checking before release?

The PR did actually fail the presubmit test (see test results in #2858 and link to test failure: https://github.com/pulumi/pulumi-kubernetes/actions/runs/8118521069/job/22193057050). Not sure why automerge merged it in despite the test failure.

I think this should be the only required change for glob settings. We only have 2 code paths that use the glob package, and scanning through the API changes in the changelog indicate we should probably be ok with the use cases in pu/kubernetes.