feat:expose renderInput in AutoCompleteInput props

[AarishMansur]

Problem

AutocompleteInput supports the renderInput prop at runtime via the underlying MUI Autocomplete component, but this prop is not exposed in the TypeScript definition of AutocompleteInputProps
As a result, TypeScript users cannot pass renderInput without losing type safety or relying on implicit typing.

Closes #10430

Solution

This PR exposes the renderInput prop in the AutocompleteInput TypeScript interface by reusing the corresponding type from MUI’s AutocompleteProps
There is no runtime behavior change this only aligns the TypeScript definition with the existing supported API.

How To Test

1. Use AutocompleteInput with a renderInput prop in a TypeScript project.

2. Verify that TypeScript does not report any type errors.

3. Run the test suite (yarn test) to ensure no regressions are introduced.

Additional Checks

• The PR targets master for a bugfix or a documentation fix, or next for a feature
• The PR includes unit tests ((not applicable typeScript only change with no runtime behavior)
• The PR includes one or several stories (not applicable no UI or behavioral change)
• The documentation is up to date(not required this prop was already supported at runtime)

Also, please make sure to read the contributing guidelines.

[fzaninotto]

I notice that the props already extend MUI's AutocompleteProps, specifically omitting renderInput. I wonder why this is, and I also wonder if a better fix wouldn't be of removing this prop from the omit array.

[fzaninotto]

No wait, I know: we don't want to support overriding the renderInput prop, as this is the heart of react-admin's AutocompleteInput. If you need a specific renderInput, I believe you should build your own AutocompleteInput.

Can you expain your use case to determine if it's something we want to support?

[slax57]

@fzaninotto It's to support the use-case described in #10430

@AarishMansur please mention the issue you are addressing when opening a PR, it helps with traceability.

[AarishMansur]

@fzaninotto

This PR is meant to support the use case described in #10430, where grouping is required and the selected option needs a richer visual representation.

[fzaninotto]

Understood, thanks for the feedback. I still think the correct implementation should be to remove the renderInput key from the Omit type instead of re-adding it later.