Decentralizing the validation domain

[CMCDragonkai]

Description

This PR decentralizes the validation domain avoiding a nexus point SPOF. Some changes to import paths will be expected.

Issues Fixed

• Fixes Decentralize the Input Validation Domain #532

Tasks

• 1. Move all parseX inside src/validation/utils.ts into their respective domains.
• 2. In each domain/utils.ts they should import the src/validation/errors.ts as validationErrors, see src/claims/utils.ts to see how to do this.
• 3. All users of src/validation/utils.ts should now be using domainUtils.parseX instead avoiding a centralised import on validation domain as a "many to many" nexus in our codebase.
• [ ] 4. We can move the src/validation/index.ts functions into src/validation/utils.ts and re-export it unscoped inside src/validation, allowing one to import { validate, validateSync } from '../validation';. - not going to do this, it's fine the way it is

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[ghost]

👇 Click on the image for a new way to code review

Legend

[CMCDragonkai]

This is weirdly breaking NodeConnectionManager.general.test.ts.

[CMCDragonkai]

This is done. The validation/utils.ts is now reduced to only parseInteger and parseNumber.

Everything else is moved into specific domains.

And of course all the parse Ids is in src/ids.

This will affect downstream PK CLI.

So now we have finally removed this big nexus point! Imports should be faster.