Add Trino 390 release notes

[colebow]

Description

Assemble the release notes for the upcoming Trino 390 release.

Is this change a fix, improvement, new feature, refactoring, or other?

Improvement

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Docs only.

How would you describe this change to a non-technical end user or system administrator?

Add the release notes for Trino 390 with sections for general, security, connectors and other topics as included in the release.

Related issues, pull requests, and links

Fixes #13119

Documentation

( ) No documentation is needed.
(✅) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(✅) No release notes entries required.
( ) Release notes entries required with the following suggested text:

Verification for each commit

Format: commit, committer/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

7 July 2022 ✅

432d289 @phd3 #13113 ✅ rn ✅ docs

8 July 2022 ✅

159b84d @ebyhr #10367 ✅ rn ✅ docs
c7b2682 @martint #13126 ✅ rn ✅ docs
6ce807f @ebyhr #13128 ✅ rn ✅ docs

9 July 2022 ✅

453a36a @ebyhr #10809 ✅ rn ✅ docs
3737ba0 @martint #12962 ✅ rn ✅ docs

10 July 2022 ✅

ddf0ed9 @ebyhr #12939 ✅ rn ✅ docs

11 July 2022 ✅

844ac19 @ebyhr #13142 ✅ rn ✅ docs
b2a6bd9 @ebyhr #11359 ✅ rn ✅ docs
241e0be @ebyhr #11359 ✅ rn ✅ docs
811ade0 @ebyhr #11359 ✅ rn ✅ docs
018e75c @ebyhr #12510 ✅ rn ✅ docs
be7a8d9 @raunaqmorarka #13123 ✅ rn ✅ docs
d98d1e9 @raunaqmorarka #13123 ✅ rn ✅ docs
812c006 @raunaqmorarka #13123 ✅ rn ✅ docs

12 July 2022 ✅

e1a0fbd @ebyhr #13068 ✅ rn ✅ docs
f8be32e @ebyhr #13068 ✅ rn ✅ docs
3494e12 @ebyhr #13068 ✅ rn ✅ docs
290e211 @ebyhr #13138 ✅ rn ✅ docs
e28f639 @ebyhr #13138 ✅ rn ✅ docs
bf7eaeb @ebyhr #13087 ✅ rn ✅ docs
1fde1ac @ebyhr #13087 ✅ rn ✅ docs
0d3c3fd @ebyhr #13153 ✅ rn ✅ docs
4af7c3c @arhimondr #12633 ✅ rn ✅ docs
0cb9524 @arhimondr #12633 ✅ rn ✅ docs
661193d @phd3 #10506 ✅ rn ✅ docs
d8c2009 @phd3 #10506 ✅ rn ✅ docs
edbf490 @phd3 #10506 ✅ rn ✅ docs
ffd0d8e @phd3 #10506 ✅ rn ✅ docs
6cff97e @phd3 #10506 ✅ rn ✅ docs
cd1240b @phd3 #10506 ✅ rn ✅ docs
063b240 @phd3 #10506 ✅ rn ✅ docs
4aedf4d @phd3 #10506 ✅ rn ✅ docs
43d831c @ebyhr #13156 ✅ rn ✅ docs
91ce0ec @ebyhr #13141 ✅ rn ✅ docs
345ee15 @ebyhr #12631 ✅ rn ✅ docs
06e7526 @martint #13152 ✅ rn ✅ docs

13 July 2022 ✅

ad86377 @ebyhr #13143 ✅ rn ✅ docs
05b5c95 @ebyhr #13159 ✅ rn ✅ docs
fe72c3c @ebyhr #11915 ✅ rn ✅ docs
6081e7d @ebyhr #11915 ✅ rn ✅ docs
af73f3b @ebyhr #11915 ✅ rn ✅ docs
e73567b @ebyhr #11915 ✅ rn ✅ docs
cb703eb @ebyhr #11915 ✅ rn ✅ docs
902f4c9 @ebyhr #13081 ✅ rn ✅ docs
1936ebe @ebyhr #13147 ✅ rn ✅ docs
78f0e8a @ebyhr #13147 ✅ rn ✅ docs
2c573a2 @ebyhr #13147 ✅ rn ✅ docs
da4ad60 @ebyhr #13147 ✅ rn ✅ docs
8de920e @ebyhr #13161 ✅ rn ✅ docs
ca7dcaa @ebyhr #13161 ✅ rn ✅ docs

14 July 2022 ✅

c2d1f2a @ebyhr #13171 ✅ rn ✅ docs
bc7a4ee @ebyhr #13172 ✅ rn ✅ docs
794222f @ebyhr #13174 ✅ rn ✅ docs
cc86d3f @ebyhr #13174 ✅ rn ✅ docs
9b92233 @Praveen2112 #13009 ✅ rn ✅ docs
d78c38b @martint #13014 ✅ rn ✅ docs
b0dcb8d @martint #13014 ✅ rn ✅ docs
da367a3 @martint #13014 ✅ rn ✅ docs

[martint]

Doesn't "disallow" imply that it will produce an error, too?

[colebow]

Yeah, I think this PR introduces better error handling, but it's still an error. Probably not needed to be included in release notes?

[ebyhr]

Probably not needed to be included in release notes?

Disagreed. Previously, we could set a database in connection-url without error. This is user facing change.