Server Error: Invalid src prop (https://avatars.githubusercontent.com/u/67109815) on `next/image`

Error: Invalid src prop (https://avatars.githubusercontent.com/u/67109815) on `next/image`, hostname "avatars.githubusercontent.com" is not configured under images in your `next.config.js`
See more info: https://nextjs.org/docs/messages/next-image-unconfigured-host

Why would this need to be a **`Server Error`**?
A perfectly valid image that should "just work" throws an Error!
And not a _helpful_ one, that anyone could debug by locating the line reference.
Nope, if you saw this in an a `Next.js` app, you'd have to _`find`_ this `string` in the codebase to fix it.

For context this is the invocation:
```jsx

```
The image is just the `TailwindCSS` logo:
Which as you can see here, renders perfectly fine in a `GitHub` issue without any additional _configuration_ ... 🙄
This framework is _unnecessarily_ hostile to the `people` _using_ it.
People _accept_ it when they _really_ shouldn't!!
People using `Next.js` suffer from _severe_ [Stockholm syndrome](https://en.wikipedia.org/wiki/Stockholm_syndrome). 🤦‍♂️

The _correct_ behaviour should be _any_ image works if it's a valid URL.
And if a team/company using `Next.js` _needs_ to "lock down" the sources of images,
_that's_ when they add a config option in the `next.config.js` to only allow certain origins!

This happens to be on a `Nextra` (documentation) site where we are displaying the logos of the "[Tech Stack](https://github.com/dwyl/technology-stack)".
It doesn't need to be "locked down" and given that `Nextra` is just rendering `.md`/`.mdx` files this standard markdown works:

```md
```

Forcing me/us to add _another_ line to our `next.config.js` just to _allow_ this image to be rendered is _lame_. 🤦‍♀️