Fix release workflow

[arboleya]

After the introduction of #3190, the release workflows (#1, #2) started failing silently.

The new version is published to NPM, but the next and latest tag and the release is not created on GitHub.

In the Release to @next tag on Npm step, there's this error:

Already on 'master'
M	packages/fuels/src/cli/commands/deploy/proxy/types/Src14OwnedProxy.ts
M	packages/fuels/src/cli/commands/deploy/proxy/types/Src14OwnedProxyFactory.ts
M	packages/fuels/src/cli/commands/deploy/proxy/types/common.d.ts
M	packages/fuels/src/cli/commands/deploy/proxy/types/index.ts
Your branch is up to date with 'origin/master'.
sed: can't read .changeset/odd-starfishes-flash.md
.changeset/popular-bikes-allow.md
.changeset/serious-crabs-begin.md
.changeset/tame-moons-clean.md: No such file or directory
No packages affected by changesets, skipping release to @next tag

These dirty files are in this state because we generate and ship types for the proxy contract:

fuels-ts/packages/fuels/package.json

Lines 54 to 55 in 8321098

	"build": "run-s build:proxy build:package build:browser build:minified",
	"build:proxy": "tsx scripts/build-proxy-contract.ts",

There was an unsuccessful attempt to fix the issue via this PR, but it was a miss:

• chore: regenerate proxy artifacts during release #3221