🎩 What? Why?

This fixes some illogical heading orders with the budgets component.

As a sidenote, I think the budget component's index view that lists the budgets should have a <h2> level heading before the budgets listing. Now it only has a <h2> at the "my budgets" section which is confusing as the rest of the budgets does not have any heading. The screen reader user may think that all of the budgets are "my budgets" because they are under the same <h2> level heading. But this is another discussion as it is a change in functionality.

WCAG 2.2 / 1.3.1 Info and Relationships (Level A)

https://www.w3.org/TR/WCAG22/#info-and-relationships
https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html

Testing

Check the heading orders in the budgets list view.

📋 Checklist

• ❓ CONSIDER adding a unit test if your PR resolves an issue.
• ✔️ DO check open PR's to avoid duplicates.
• ✔️ DO keep pull requests small so they can be easily reviewed.
• ✔️ DO build locally before pushing.
• ✔️ DO make sure tests pass.
• ✔️ DO make sure any new changes are documented in docs/.
• ✔️ DO add and modify seeds if necessary.
• ✔️ DO add CHANGELOG upgrade notes if required.
• ✔️ DO add to GraphQL API if there are new public fields.
• ✔️ DO add link to MetaDecidim if it's a new feature.
• ❌AVOID breaking the continuous integration build.
• ❌AVOID making significant changes to the overall architecture.