ReturnType is lost after a simple wrapper function

Nadie ha tomado este issue todavía.

### 🔎 Search Terms

ReturnType changes to any, wrapper function losing inferred types

### 🕗 Version & Regression Information

- This changed between versions ______ and _______
- This changed in commit or PR _______
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about YES
- I was unable to test this on prior versions because _______

### ⏯ Playground Link

https://codesandbox.io/p/devbox/lingering-fog-5fhtrv

### 💻 Code

```ts
const { useGetPokemonByNameQuery } = pokemonApi;

// Wrapper to demonstrate the issue
export const useGetPokemonByNameQueryWrapper = (
...parameters: Parameters
) => {
return useGetPokemonByNameQuery(...parameters);
};

const useTest = () => {
// data1 has type Pokemon | undefined as expected
const { data: data1 } = useGetPokemonByNameQuery("pikachu");

// data2 has type any???
const { data: data2 } = useGetPokemonByNameQueryWrapper("pikachu");
};
```

### 🙁 Actual behavior

When I wrap any query hook generated by Redux Toolkit Query with any simple wrapper function the return type stops being inferred and changes to 'any'. Check the example in the attached Sandbox in file `/src/services/pokemon.ts`

### 🙂 Expected behavior

I expect the wrapper function to preserve the return type of the wrapped function and to correctly infer it.

### Additional information about the issue

_No response_

Comienza con la reproducción en el CodeSandbox enlazado, especialmente en /src/services/pokemon.ts, y compara los tipos inferidos del hook de consulta directo y de su wrapper. Ejecuta el ejemplo e inspecciona por qué data2 se convierte en any; la tarea estará terminada cuando el wrapper conserve el tipo de retorno inferido del hook envuelto.

Escrito por el modelo de indexación a partir del texto del issue.