chore: move Hasher package into Crypto

[airope]

Description

Moves the @fuel-ts/hasher package functionality into @fuel-ts/crypto, as proposed in #2477.

Changes

• Moved hasher.ts (and its tests) into packages/crypto/src/
• Updated @fuel-ts/crypto index to re-export all hasher functions (sha256, hash, uint64ToBytesBE, hashMessage, HashableMessage)
• Updated all imports across the monorepo from @fuel-ts/hasher to @fuel-ts/crypto
• Updated package.json dependencies accordingly
• Kept @fuel-ts/hasher package as a thin re-export wrapper from @fuel-ts/crypto for backward compatibility
• Removed duplicate re-exports in packages/fuels/src/index.ts

Closes #2477

[fuel-cla-bot]

Thanks for the contribution! Before we can merge this, we need @arboleya @danielbate @Torres-ssf @Dhaiwat10 to sign the Fuel Labs Contributor License Agreement.

[cursor]

PR Summary

High Risk
High risk because it substantially changes the release/publishing and CI workflows (npm publishing via provenance/OIDC, CodeArtifact pr-*/next publishing, Vercel deployments, and test gating), which can easily break automation or ship incorrect artifacts if misconfigured.

Overview
CI/release automation is reworked: adds a new changesets-pr workflow for versioning PRs, switches PR/next publishing to AWS CodeArtifact (publish-to-next), updates release.yaml to publish only on ci(release): commits with npm provenance/OIDC, adds Vercel deploy composites + workflows for PR previews and release deployments, and introduces a deprecate-versions workflow (removing older PR-release/unpublish automation and trimming Dependabot config).

Template + dev tooling updates: migrates apps/create-fuels-counter-guide from Next.js to Vite/React (new app structure, env vars, Tailwind 4, Playwright UI tests, and adds a Sway script plus contract/predicate tests), updates local fuel-core chain/state configs, and refreshes repo hygiene (ESLint/Prettier/ignore rules, .env.example keys, new issue templates, CODEOWNERS, CODE_OF_CONDUCT.md, and expanded SECURITY.md).

^{Written by Cursor Bugbot for commit 408b35d. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Duplicate useNotification() hook calls in components

Medium Severity

Each of Contract, Script, and Predicate components calls useNotification() twice — once with destructuring on the line above and once as a bare standalone call whose return value is discarded. The extra call creates an orphaned useRef and unused closures on every render. Since useNotification manages toast state via a ref, this silently wastes resources and is clearly leftover from a refactor.

Additional Locations (2)

• apps/create-fuels-counter-guide/src/components/Script.tsx#L12-L13
• apps/create-fuels-counter-guide/src/components/Predicate.tsx#L13-L14

 

[cursor]

Feature template YAML has broken indentation

Medium Severity

The first list item under body: uses - type: markdown at zero indentation (line 5), while subsequent items like - type: textarea (line 13) use 2-space indentation. Comparing with the correctly formatted 1-bug.yaml, the dash on line 5 needs to be indented by 2 spaces to be a proper child of body:. This malformed YAML will cause GitHub to fail parsing the feature request issue template.