fix: meta transaction was signing the incorrect payload

[Elabar]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• Commit messages follow the conventional commits spec
• If this is a code change: I have written unit tests.
• If this changes code in a published package: I have run pnpm changeset to create a changeset JSON document appropriate for this change.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Details

signDelegateAction was signing incorrect payload and making meta transaction failing in latest version.

[changeset-bot]

🦋 Changeset detected

Latest commit: 88af787

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages

Name	Type
@near-js/signers	Patch
@near-js/cookbook	Patch
@near-js/accounts	Patch
@near-js/biometric-ed25519	Patch
@near-js/client	Patch
@near-js/crypto	Patch
@near-js/iframe-rpc	Patch
@near-js/keystores-browser	Patch
@near-js/keystores-node	Patch
@near-js/keystores	Patch
@near-js/providers	Patch
@near-js/tokens	Patch
@near-js/transactions	Patch
@near-js/types	Patch
@near-js/utils	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[denbite]

looks good to me, let's only include near-api-js into the changeset file as a patch

[denbite]

@Elabar I meant to add near-api-js next to @near-js/signers, not replace it

---
"near-api-js": patch
"@near-js/signers": patch
---

it's needed to explicitly add near-api-js to changesets, because whenever you upgrade one of @near-js/* packages, it doesn't trigger an update for near-api-js automatically, even though it depends on them

[Elabar]

@denbite opps, sorry about that. I'm not familiar with changeset at all 🤣

I have updated it again, can you check?