KCM header/footer should not include padding or separator
Currently, KCMs provide padding and a separator for the header/footer.
This is a blocker for using Kirigami.InlineMessage's header/footer position in the footer, as they expect to be able to fill the header/footer as they can currently with a Kirigami.Page:
Such a change would need us to review all uses of every KCM's header/footer. KCMs that want padding and a separator would need to be changed to include their own.
This would likely be tricky to do at once as Frameworks and Plasma do not ship simultaneously.
Edited by Oliver Beard