fix: re-enable noParamaterReAssign and fix linting

[ChefBingbong]

Motivation
This PR takes care of a pending task, which is to re-enable the biome noParamaterReAssign style lint and to fix all instances in the codebase where this rule is breached

changes

1. Re-enabled biome's noParamaterReAssign
2. fixed all places where this rule was breached,
3. ensured the lint command in root runs with no warnings
4. ensured all test suites remained unaffected by the relevant code changes

[CLAassistant]

All committers have signed the CLA.

[nazarhussain]

Please make sure to reflect this change only for functions where parameters are really reassigned within function.

[nazarhussain]

I don't see valueBN is been reassigned anywhere in this function. Also primitives as parameters is not an issue to be assigned anyway.

[ChefBingbong]

Hi there @nazarhussain . thanks for your comment. Actually it is being reassigned here

https://github.com/ChefBingbong/ssz/blob/53591ed4ca031dee9f1305c775eab4096675568c/packages/persistent-merkle-tree/src/node.ts#L289

in the last else of the function.

also this pr tackles this issue. so this is the motivation behind these changes

ssz/biome.jsonc

Lines 19 to 20 in 1a34fe8

	// TODO: There are two many usages, will fix in separate PR
	"noParameterAssign": "off",

re-enabling this biome flag requires these locations (i.e this prs changes) to be fixed. however i made sure that the the changes are compatabile with the current test suiting and dont change expected code functionality

[nazarhussain]

The changes related to primitives should be removed. All values of number, bigint or any other primitive is passed by value, so no issue if these are reassigned in local function scope.

We should focus the changes only object or complex types where accidental parameter change have any side effect.