v4: parse and safeParse no longer accept path in params

[arg0NNY]

This was helpful when validating some specific deeply-nested properties inside an object without worrying about manually altering the path in the root and union issues for it to be a valid path relative to the root object and just simply handling issues as-is.

Here's the ParseParams interface in v3 used by parse and safeParse:

zod/src/helpers/parseUtil.ts

Lines 43 to 47 in 8cca93b

	export type ParseParams = {
	path: (string | number)[];
	errorMap: ZodErrorMap;
	async: boolean;
	};

I couldn't find any mentions of this change in the migration guide so I assume it was unintentional.

[arg0NNY]

Also, path is no longer available inside transforms and refinements' ctx, which was crucial for recursive types to make validations based on the current path. Notify me if I should create a separate issue for this.