Modernize gauge typescript plugin

[zabil]

• Update remove old unmaintained packages
• Add new linter and formatter
• Upgrade to typescript 5
• Use npx to launch ts-node in the runner
• Use grpc client for testing instead of mocking
• Use npm workspaces to add and run functional tests

[zabil]

@BugDiver appreciate it if you can take a quick look at this PR. It uses npm workspaces now to add better testing. I've modified the token in the settings to publish to gauge -ts. So hopefully this should publish on merge. 🤞

[zabil]

Removing eslint and migrating to https://biomejs.dev as it's faster and supports formatting too.

[zabil]

Over here the major changes are upgrading to node 20 as well as splitting the jobs into running unit test of gauge-ts and an e2e test which runs a sample gauge spec that refers to the gauge-ts package. This way it can check if changes affect gauge specs.

[zabil]

Remove some old badges and change bugdiver to getgauge. Hope that's ok.

[zabil]

This is a new npm workspace project for running e2e tests. It refers to gauge-ts but runs gauge specs.

[zabil]

Big changes here. The new protobuf implementation prevents describing anything other that rpc methods so we can't add custom fields. So you can see processors stored as static fields instead.

[zabil]

@BugDiver Also how does release work? I don't see a release candidate label.

[BugDiver]

@BugDiver Also how does release work? I don't see a release candidate label.

The release was not automated for this repo, I always published it manually.
There is an release Action which perform the release, but trigger mechanism for that action was manual.
I have forgotten how we automated the release for other repos 🥺, let me jog my memory,
I 'll update the release mechanism.

[BugDiver]

Here is the script which is used to trigger the release action
https://github.com/getgauge/gauge-ts/blob/main/release.sh

[zabil]

I 'll update the release mechanism.

Ah ok, that'll be great!

[BugDiver]

I guess the ReleaseCandidate (defined at org level) is not showing up for this repo, because if was transferred, and not created.

[gaugebot]

@zabil Thank you for contributing to gauge-ts. Your pull request has been labeled as a release candidate 🎉🎉.

Merging this PR will trigger a release.

Please bump up the version as part of this PR.

Instructions to bump the version can found at CONTRIBUTING.md

If the CONTRIBUTING.md file does not exist or does not include instructions about bumping up the version, please looks previous commits in git history to see what changes need to be done.