Auto Semantic tags for template parts header, footer

[Odinnh]

What problem does this address?

Currently for footer and header template parts, you need to specifically set the default tags in a convoluted way, or through code.
the current method to change the tag is to set it in each template to the area "header"/"footer" and the html element to the specific tag"header"/ "footer", the automatic tagging does not function properly.

What is your proposed solution?

We have a setting in theme.json to define template parts, a.e.;

...
{
	"area": "header",
	"name": "header",
	"title": "Header"
},
{
	"area": "footer",
	"name": "footer",
	"title": "Footer"
}
...

my proposal is to either for every area "footer"/"header", forcibly set the tags to the semantic ones,
or to have an option to set the tagname in the definitions in templateParts

a.e.

...
{
	"area": "header",
	"name": "header",
	"title": "Header",
	"tagName": "header" // default, header, main, aside, footer ....
},
...

[jasmussen]

Template parts now automatically use the semantic tag defined by their area (area_tag) when no explicit tag is set: header areas render as <header>, footer as <footer> (#62785, WP 6.6).