Harmonize release notes to new mandatory labels

[brisvag]

Description

Harmonizes our release notes to the new labels enforced by napari/napari#5733

Type of change

• Fixes or improves existing content
• Adds new content page(s)
• Fixes or improves workflow, documentation build or deployment

cc @psobolewskiPhD

[Czaki]

Single questions. We start having automated Pr (like napari/napari#5788). We want to exclude them from release notes (it they contains only constraints update, without code bugfixes)?

[psobolewskiPhD]

I think better to put in maintenance?
I mean in some cases someone will have to fix a test, so there will be some real work even if PR is automated.

[Czaki]

I think about two labels.

For example:

• maintenance - included in release docs
• automatic maintenance - not included in docs.

So if someone fixes the tests, then will change the label

[psobolewskiPhD]

Is it worth the complexity? will people remember to change it? 👀

[brisvag]

I'm for a single maintenance label, which goes in the notes. Most people will ignore that section anyways, so that's fine.

[brisvag]

@psobolewskiPhD did you also get around to deleting labels as we discussed?