Feature/uppsf 5919

[asparuhft]

Description

What

Remove the synchronisation between PAC and publishing

Why

JIRA Ticket UPPSF-5919

Anything, in particular, you'd like to highlight to reviewers

Mention here sections of code which you would like reviewers to pay extra attention to .E.g

Would appreciate a second pair of eyes on the test
I am not quite sure how this bit works
Is there a better library for doing x

Scope and particulars of this PR (Please tick all that apply)

• Tech hygiene (dependency updating & other tech debt)
• Bug fix
• Feature
• Documentation
• Breaking change
• Minor change (e.g. fixing a typo, adding config)

DoD - Ensure all relevant tasks are completed before marking this PR as "Ready for review"

• Test coverage is not significantly decreased
• All PR checks have passed
• Changes are deployed on dev before asking for review
• Documentations remains up-to-date
  • OpenAPI definition file is updated
  • README file is updated
  • Documentation is updated in upp-docs and upp-public-docs
  • Architecture diagrams are updated

---

This Pull Request follows the rules described in our Pull Requests Guide

[coveralls-official]

coverage: 79.72% (+6.8%) from 72.906%
when pulling a90a11e on feature/UPPSF-5919
into 67a5a2d on master.