Remove outdated & possibly confusing statement about redirects (#33224)

## Documentation / Examples

- [x] Make sure the linting passes by running `yarn lint`

The statement I have removed may be misleading. A colleague of mine has interpreted it as ‘we need to create a custom page or `<Link href="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/redirect-path" />` won’t work on the client’. I just ran `npx create-next-app --example redirects redirects-app` and confirmed that this was not necessary.

So saying that redirects “do not affect client-side routing” is probably wrong. They do and they do it the right way.

Author: kachkaev

docs/api-reference/next.config.js/redirects.md

@@ -23,8 +23,6 @@ description: Add redirects to your Next.js app.
 
 Redirects allow you to redirect an incoming request path to a different destination path.
 
-Redirects are only available on the Node.js environment and do not affect client-side routing.
-
 To use Redirects you can use the `redirects` key in `next.config.js`:
 
 ```js