Update core versions table: v1.0 EOL, into 2023

[jtcohen6]

Apparently we're going to keep building dbt-core, and releasing some more versions next year!

Also, v1.0 reached End Of Life on Dec 3 (#2449). It's no longer under "official support," meaning that v1.0.8 was its final patch release; there won't be any others.

Questions:

• Should we split up into multiple tables: currently supported versions, future versions, no-longer-supported versions?
• Support in dbt Cloud: We're still doing "soft" drawdowns of old versions; we aren't yet in a place of forcefully upgrading accounts, or removing old versions. How should we reflect that on the docs site? Here's the answer I gave a community member:

After Dec 3, we won't be releasing any new patches of v1.0.x, we won't be providing the same level of ongoing support in Cloud, and we'll strongly encourage you to upgrade to a newer version. I'm hoping it's a relatively painless upgrade — there should be minimal friction, and zero breaking changes.

[netlify]

✅ Deploy Preview for docs-getdbt-com ready!

Name	Link
🔨 Latest commit	56eba92
🔍 Latest deploy log	https://app.netlify.com/sites/docs-getdbt-com/deploys/63908e99e72a810009ca9dd0
😎 Deploy Preview	https://deploy-preview-2516--docs-getdbt-com.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[mirnawong1]

hey @jtcohen6 was going to have a look at this but may be best for @matthewshaver to review it as we discussed versioning yesterday. since it's related to core and versioning - you may have more ideas, Matt!

[jtcohen6]

Closing in favor of #2534, which will do this & a whole lot more!