'use client' in client icons and IconContext
<!-- BEFORE YOU REPORT -->
<!-- 1. Search for existing issues! If the issue has already been reported, add a 👍 or a comment to help show your interest. -->
<!-- 2. If your issue pertains to a specific library, please leave it on the relevant repository! -->

**Describe the bug**

Not really a bug, but rather a feature request. 

When using an icon with Next.js App Router, one would need to either use the server component version (under `/dist/ssr`) or make the outer component a client component. The former doesn't support the use of `IconContext`, and the latter is a mild inconvenience. Would be very nice to be able to use the client icons directly inside server components. 

An approach to this is to have `'use client'` at the top of every client icon file and introduce a `IconProvider` component (with `use client`), which simply forwards all icon props to the underlying `IconContext`. I am unsure if these additions will make for a breaking change, but they are pretty straightforward for massive DX improvement. 

A React Server Component can then be written concisely like so:

```
// page.tsx
import { IconProvider, User as UserIcon } from '@phosphor-icons/react';

export default function UserPage() {
  return (
    <IconProvider size={20}>
      <div className="blah blah">
        <UserIcon />
      </div>
    </IconProvider>
  );
}
```

**Steps to Reproduce**

N/A

<!-- Steps to reproduce the behavior. -->

**Expected behavior**

<!-- A clear and concise description of what you expected to happen. -->

N/A

**Screenshots**

<!-- If applicable, add screenshots to help explain your problem. -->

N/A

**Context (please complete the following information):**

N/A

<!--
- OS: [e.g. Windows 10]
- Browser/Environment [e.g. chrome, safari, node]
- Library [e.g. @phosphor-icons/react]
- Version [e.g. 2.1.0]
-->

**Additional notes**

<!-- Add any other context about the problem here. -->

I can certainly help with this, but need to know any potential implications on users who don't use React Server Components or Next.js
