fix: specify env.ts more specifically for newer node versions

[wdoconnell]

Module resolution has changed with Node 23.6.0. Node permits importing ESM with require statements, but require statements now require specifying rather than inferring a file extension. This breaks production builds with Node versions >= 23.6.0. Thank you to @philjb for identifying this.

Checklist

Authors and Reviewer(s), please verify the following:

• A PR description, regardless of the triviality of this change, that communicates the value of this PR
• Well-formatted conventional commit messages that provide context into the change
• Documentation updated or issue created (provide link to issue/PR)
• Signed CLA (if not already signed)
• Feature flagged, if applicable

[david-rusnak]

🎉

[philjb]

I'm glad it wasn't just on my machine! thanks for your help.

[jdstrand]

I'm glad it wasn't just on my machine! thanks for your help.

I'll also note (to state the obvious) that we use node LTS releases (which 23 is not one of them) which is why this didn't show up in CI. 24 will be the next LTS soon, so it's good to fix this. Thanks @philjb and @wdoconnell!

[philjb]

I dunno what to make of this monitor-ci failure in the remocal-smoke-test

curl: (77) error setting certificate verify locations:  CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs
sha256sum: /usr/local/bin/kubectl: No such file or directory
/usr/local/bin/kubectl: FAILED open or read
sha256sum: WARNING: 1 listed file could not be read

Exited with code exit status 1

[jdstrand]

@philjb - @wdoconnell noticed this and asked Opeyemi to take a look (as it has something to do with k8s-idpe).