Add Trino 409 release notes

[colebow]

Description

Assemble the release notes for the upcoming Trino 409 release. Fixes #16247

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

Verification for each pull request

Format: maintainer, PR/issue number, ✅ / ❌ rn ✅ / ❌ docs
✅ rn - release note added and verified, or assessed to be not necessary, set to ❌ rn before completion
✅ docs - need for docs assessed and merged, or assessed to be not necessary, set to ❌ docs before completion

23 Feb 2023

@martint #15999 ❌ rn ✅ docs
@ebyhr #15868 ✅ rn ✅ docs
@ebyhr #16208 ✅ rn ✅ docs
@martint #16242 ✅ rn ✅ docs

24 Feb 2023

@hashhar #16185 ✅ rn ✅ docs
@losipiuk #16114 ✅ rn ✅ docs
@arhimondr #15375 ✅ rn ✅ docs
@electrum #16231 ✅ rn ✅ docs
@ebyhr #16255 ✅ rn ✅ docs

25 Feb 2023

@dain #15918 ✅ rn ❌ docs
@losipiuk #16220 ✅ rn ✅ docs
@dain #16270 ✅ rn ❌ docs
@martint #16224 ✅ rn ✅ docs

26 Feb 2023

@ebyhr #16077 ✅ rn ✅ docs
@kokosing #16169 ✅ rn ✅ docs
@electrum #16226 ✅ rn ✅ docs
@ebyhr #16193 ✅ rn ❌ docs

27 Feb 2023

@kokosing #16276 ❌ rn ✅ docs
@kokosing #16260 ✅ rn ✅ docs
@findepi #16016 ✅ rn ✅ docs
@ebyhr #16279 ✅ rn ✅ docs
@ebyhr #16254 ✅ rn ✅ docs
@ebyhr #15995 ✅ rn ✅ docs
@ebyhr #16002 ✅ rn ❌ docs
@ebyhr #16274 ✅ rn ✅ docs
@ebyhr #16285 ✅ rn ✅ docs
@dain #16271 ✅ rn ❌ docs

28 Feb 2023

@findepi #14891 ✅ rn ✅ docs
@findepi #15930 ✅ rn ✅ docs
@ebyhr #16294 ✅ rn ✅ docs
@ebyhr #16278 ✅ rn ✅ docs
@kokosing #16259 ✅ rn ✅ docs
@kokosing #16281 ✅ rn ✅ docs
@raunaqmorarka #16267 ✅ rn ✅ docs
@raunaqmorarka #16120 ✅ rn ➖ docs
@findepi #16300 ✅ rn ✅ docs
@electrum #15637 ✅ rn ✅ docs
@electrum #16304 ✅ rn ✅ docs
@electrum #16243 ✅ rn ✅ docs
@ebyhr #16297 ✅ rn ✅ docs
@ebyhr #16261 ✅ rn ✅ docs
@electrum #16290 ✅ rn ✅ docs

1 Mar 2023

@ebyhr #16313 ✅ rn ✅ docs
@ebyhr #16318 ✅ rn ✅ docs
@ebyhr #16251 ✅ rn ✅ docs
@hashhar #16305 ✅ rn ✅ docs
@findepi #16295 ✅ rn ✅ docs
@ebyhr #16322 ✅ rn ✅ docs
@phd3 #16312 ✅ rn ✅ docs
@phd3 #14837 ✅ rn ✅ docs
@kokosing #16323 ✅ rn ✅ docs
@martint #16309 ✅ rn ✅ docs
@ebyhr #16326 ✅ rn ✅ docs
@raunaqmorarka #16201 ✅ rn ✅ docs
@raunaqmorarka #15927 ✅ rn ✅ docs
@ebyhr #16334 ✅ rn ✅ docs
@ebyhr #16344 ✅ rn ✅ docs
@findepi #16310 ✅ rn ✅ docs

2 Mar 2023

@raunaqmorarka #16229 ✅ rn ✅ docs
@raunaqmorarka #16264 ✅ rn ✅ docs
@ebyhr #16327 ✅ rn ✅ docs
@findepi #16331 ✅ rn ✅ docs
@ebyhr #16345 ✅ rn ✅ docs
@ebyhr #16339 ✅ rn ✅ docs
@raunaqmorarka #16329 ✅ rn ✅ docs
@ebyhr #16341 ✅ rn ✅ docs
@electrum #16350 ✅ rn ✅ docs

3 Mar 2023

@sopel39 #15892 ✅ rn ✅ docs
@ebyhr #16330 ✅ rn ✅ docs
@ebyhr #15802 ✅ rn ✅ docs
@kokosing #16090 ❌ rn ✅ docs

[martint]

"native" is a little misleading. Should we say "optimized", "dedicated", "custom", etc.? cc @dain

[colebow]

The configuration properties are all named native, so if 'native' is misleading, we probably need to rename all of those.

[mosabua]

Looks good now.