Separate post-footer for better customization

[Beryesa]

What does this PR change? What problem does it solve?

Separates post-footer into post_footer.html for better customization Leaves less room for git conflicts and unnecessary overwrites, which results in better flexibility

Was the change discussed in an issue or in the Discussions before?

Not really, but following post-meta for consistency, which is also separate

PR Checklist

• [ ] This change adds/updates translations and I have used the template present here.
• [x] I have enabled maintainer edits for this PR.
• [x] I have verified that the code works as described/as intended.
• [ ] This change adds a Social Icon which has a permissive license to use it.
• [x] This change does not include any CDN resources/links.
• [x] This change does not include any unrelated scripts such as bash and python scripts.
• [ ] This change updates the overridden internal templates from HUGO's repository.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[adityatelange]

post-meta is separate because we call it from multiple template, with post-footer it is only on one template.