update got dependency and convert to esm module

[fairclothjm]

Description

This PR proposes the following changes:

• update got to v14
• convert the project to an ESM module
• remove the jest testing framework in favor of vitest

Also, apparently ncc can't compile the jsonata dependency to ESM properly so we add a custom require to be able to import it. I may be doing something wrong here but this is what I came up with based on vercel/ncc#791

Why?

vault-action’s got v11 dependency is no longer maintained. We need to either convert to ESM or use the dynamic import() function to upgrade to v14. This PR takes the former route.

RE: jest -- The jest testing framework does not have good support for ESM modules. It requires enabling experimental features and doesn't have good support for mocking. So we swap to vitest which has full ESM support. See https://stackoverflow.com/questions/68956636/how-to-use-esm-tests-with-jest and https://jestjs.io/docs/ecmascript-modules

See #516

Alternatives

We could look into switching to another HTTP library so that we don't have to convert our project to an ESM module. However, I opted to stick with got so that we don't have to change any of the HTTP configuration and handling.

Checklist

• Added CHANGELOG entry (only for user-facing changes)

Community Note

• Please vote on this pull request by adding a 👍
  reaction
  to the original pull request comment to help the community and maintainers
  prioritize this request
• Please do not leave "+1" comments, they generate extra noise for pull request
  followers and do not help prioritize the request

[fairclothjm]

We actually do need to commit the distribution files so that each PR's e2e tests run against the changes.

[fairclothjm]

This dep update is the reason for this monster PR. 😶‍🌫️

[thyton]

Thank you for your effort in this dependency update! 🥇

This looks good from my initial pass. I have one comment.

[thyton]

LGTM. Thank you!

[fairclothjm]

Looks like this change has broken the action as can be seen in this comment.

Unfortunately, our E2E tests and local tests don't reveal this issue. It has something to do with the fact that they use the local path:

uses: ./

But I am not sure exactly why that succeeds and the following fails:

uses: hashicorp/vault-action@main

However, there is good news. (1) This change wasn't released yet and (2) It looks like there is experimental support for require()-ing synchronous ES modules in Node.js from nodejs/node#51977 which should be available in the next major node Version (v22?). That should allow us to revert this PR and import got v14.