migrate remaining scripts from yarn to pnpm

[radumojic]

Issue/Feature

• migrate remaining scripts from yarn to pnpm

Contains breaking changes

• No
• Yes

Updated CHANGELOG

• No
• Yes

Testing

• User testing
• Unit tests

[gemini-code-assist]

Code Review

This pull request migrates the project from Yarn to pnpm, updating the documentation, changelog, and integration scripts. The review feedback highlights a critical issue in the integration script where pnpm install --no-frozen-lockfile must be executed after yalc add to ensure the local package is correctly symlinked before building.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

When migrating from Yarn to pnpm, yalc add modifies package.json to point to the local .yalc directory, but pnpm's content-addressable store and symlink structure require a subsequent pnpm install to actually link the package in node_modules. Without running pnpm install after yalc add, the build step will use the registry version of @multiversx/sdk-dapp instead of the locally built one. Since package.json was modified, run pnpm install --no-frozen-lockfile before building.

Suggested change

	pnpm build-devnet
	pnpm install --no-frozen-lockfile
	pnpm build-devnet

[gemini-code-assist]

Similarly, for mx-template-dapp-nextjs, pnpm install --no-frozen-lockfile must be run after yalc add to ensure the local package is correctly symlinked in node_modules before building.

Suggested change

	pnpm build:devnet
	pnpm install --no-frozen-lockfile
	pnpm build:devnet