docs: Add note about using use hook in useContext documentation

[vishal-tambi]

In order to increase developers' awareness of the use() hook's ability to read from context, particularly in the context of React Server Components (such as Next.js apps), this PR adds a note to the useContext documentation page.

📌 Why has this changed?
Only Client Components can use useContext().

Use() offers greater flexibility, async values, and support for Server Components.

This note assists developers in avoiding misunderstandings and provides guidance on which hook to use based on the type of component.

[facebook-github-bot]

Hi @vishal-tambi!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[rickhanlonii]

Thanks but unfortunately this isn't accurate in a couple ways.

First, use(Context) can be used without a RSC framework. Any app can use use(Context) today.

Second, even in RSC frameworks, you can't use(Context) in Server Components, only Client Components.

Closing because we're already working on a use(Context) note in #7728.

[vishal-tambi]

Thanks a lot for letting me know that, I'm trying my best to update my knowledge.
Next time, I will try my best and ensure I am providing exact information .

[rickhanlonii]

@vishal-tambi no worries, it's a common misunderstanding!