chore(validator): use generic template for ConstraintOptions across validator constraint option types

[EmanFateen]

Q	A
License	GPLv3
Issue	Closes #168

Overview

This PR introduce a generic template type to be used in the ConstraintContext for ConstraintOptions.

Changes made

1. Generalised ConstraintOptions in ConstraintContext

export type ConstraintContext<TOptions extends ConstraintOptions = ConstraintOptions> = {
  path: string;
  root: unknown;
  value: unknown;
  constraint: string;
  options: TOptions;
  runNestedRules: (value: unknown, schema: FieldSchema, path: string) => Violation[];
};

2. It also affected the ConstraintValidator to be

export type ConstraintValidator<TOptions extends ConstraintOptions = ConstraintOptions> = (
  value: unknown,
  context: ConstraintContext<TOptions>,
) => Violation[];

3. Used the related options type for each constraint validator

export function notBlank(value: unknown, context: ConstraintContext<NotBlankOptions>)

export function email(value: unknown, context: ConstraintContext<EmailOptions>) 

export function slug(value: unknown, context: ConstraintContext<SlugOptions>) 

Clarification:

I did not add dedicated type-only test cases because this change is validated by the TypeScript compiler during npm run build.
The runtime behavior is unchanged, and the existing behavior tests continue to cover the validator execution path.