docs: add initial examples

[Barbapapazes]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR will add examples for an upcoming 101 article about ofetch (unjs/website#108). In order to use the last version of ofetch, I create pnpm workspace.

I order to avoid regression in articles, I think we could add an action to check types of examples!

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

Merging #288 (0eb629b) into main (3482a56) will not change coverage.
The diff coverage is n/a.

❗ Current head 0eb629b differs from pull request most recent head 3dd4afe. Consider uploading reports for the commit 3dd4afe to get more accurate results

@@           Coverage Diff           @@
##             main     #288   +/-   ##
=======================================
  Coverage   92.00%   92.00%           
=======================================
  Files           5        5           
  Lines         450      450           
  Branches      102      102           
=======================================
  Hits          414      414           
  Misses         36       36           

[Barbapapazes]

Suggested change

	To learn more, you can read the [ofetch first hand tutorial on unjs.io](https://unjs.io/resources/learn/ofetch-101-firs-hand).
	To learn more, you can read the [ofetch first hand tutorial on unjs.io](https://unjs.io/resources/learn/ofetch-101-first-hand).

[pi0]

Thanks for working on this and sorry got delayed to review. I have made a couple of reactors in order to keep changes minimal allowing to iterate over examples idea (once the article is ready, we can see what else is needed to make them running easier for users, i am thinking of some tooling...)