Calendar: Improve type declaration using generic types with default parameters

[iamkyrylo]

Describe the bug

I've encountered a problem while working with the Calendar component and creating an uncontrolled wrapper around it. The issue lies in the current type overloading approach used in the type definition:

export type CalendarProps = CalendarPropsRange | CalendarPropsMultiple | CalendarPropsSingle;

This implementation makes it difficult to dynamically manage the selectionMode without introducing additional boilerplate.

Reproducer

https://stackblitz.com/edit/vitejs-vite-7rwuaddq?file=src%2FApp.tsx

System Information

"primereact": "^10.9.1"
"react": "^18.3.1"

Steps to reproduce the behavior

1. Check typescript errors in the provided codesandbox

Expected behavior

I propose replacing the type overloading approach with generic types that include default parameters. This change will enhance the flexibility and usability of the CalendarProps type.

Example:

export interface CalendarProps<
    TMode extends CalendarSelectionMode = 'single',
    TValue = TMode extends 'multiple' ? Date[] : TMode extends 'range' ? (Date | null)[] : Date
> extends CalendarBaseProps {
    selectionMode?: TMode;
    value?: Nullable<TValue>;
    onChange?(event: FormEvent<TValue>): void;
}

[iamkyrylo]

I have prepared a PR to demonstrate how this approach could be implemented effectively.