Release notes for 0.17 updated to the new format

[saubyk]

Added a table of contents at the top and various sections to navigate to, to make it easy to parse and read the release notes.

Change Description

Description of change / link to associated issue.

Steps to Test

Steps for reviewers to follow to test the change.

Pull Request Checklist

Testing

• Your PR passes all CI checks.
• Tests covering the positive and negative (error paths) are included.
• Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

• The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
• Commits follow the Ideal Git Commit Structure.
• Any new logging statements use an appropriate subsystem and logging level.
• There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our Contribution Guidelines for further guidance.

[github-actions]

Pull reviewers stats

Stats of the last 30 days for lnd:

	User	Total reviews	Time to review	Total comments
	guggero 🥇	11 ▀▀▀	1d 8h 21m ▀	23 ▀▀▀▀▀
	yyforyongyu 🥈	10 ▀▀▀	1d 20h 56m ▀	9 ▀▀
	Roasbeef 🥉	3 ▀	4d 10h 3m ▀▀	3 ▀
	ellemouton	3 ▀	6d 18h 11m ▀▀▀	0
	ProofOfKeags	2 ▀	2d 5h ▀	1
	morehouse	2 ▀	1d 2m	3 ▀
	positiveblue	1	5h 1m	0
	Crypt-iQ	1	1d 1h 55m ▀	1
	saubyk	1	7h 15m	0
	blckbx	1	50m	2
	ziggie1984	1	20h 48m	3 ▀

[Roasbeef]

Needs a rebase!

[saubyk]

Needs a rebase!

Done

[Roasbeef]

LGTM 💾

Looks good to be as a first pass, I think some of the sections that have None could be populated, but then we'd also have some duplication elsewhere. So I guess we need to think about which headings have priority over others.