feat: starter CHANGELOG for docs

[barriebyron]

This PR starts (belatedly) a docs repo CHANGELOG

Target publish before the major upgrade, let's include the notable impactful changes that our users need to know about

Highlight especially the updates that require actions from our users.

Add entries with links to the docs that have updates our users will need to be successful with Berkeley

Links will work after docs are live

Why keep a changelog?

To make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project. Docs are not versioned, but with the major upgrade, let's be sure to let our users know where they can read about the high impact technical changes.

Who needs a changelog?

People do. The users of software are human beings who care about what's in the software. When the software changes, people want to know why and how.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 5, 2024 1:32pm

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
07-oracles	⬜️ Ignored (Inspect)	Visit Preview		Mar 5, 2024 1:32pm

[barriebyron]

@halsaphi @vfrsilva and MF friends, let's particularly list the technical docs that have changes that require action from our users