[BUG] CI isn't used/reliable/circular dependency?

[dblock]

What is the bug?
Something as trivial as an upgrade of a dependency or a version can't seem to be able to rely on CI. Log4j upgrade changes were merged with failures. An attempt in upgrading to 1.17 in a similar manner as a previous commit is failing CI (#106).

What is the expected behavior?
CI should be all green for any change

Do you have any additional context?
Is this a circular dependency problem with PA?

[sruti1312]

The recent commits 940e461 and 9fcf19fmerged into 1.2 branch (log4j and version upgrades) have failing CI due to failing integration tests (spins up a docker using docker artifacts and runs the test suite). The docker artifact was not available when this change was committed (as infra team was still working on generating the artifact). The next commit bf7f59ee updates the docker artifact link and thus have a passing CI.

On commits merged into main the CI has failures due to following reasons,

1. Failing Link checker (which is fixed now as part of this PR)
2. OS Snapshot not available for 1.2.2 and 1.2.3. We should update main to 1.3 instead of using minor versions.

Currently, PA and PA-RCA have circular dependencies causing issues like failing CI's like 6cebefab9 and making release process tedious. PA-RCA is a standalone application/library that PA depends on.
PA-RCA CI's checks out PA and run its unit tests which can be removed. Additionally the integration tests which run as a part of PA-RCA CI need to be moved to PA CI's. Tracking fixing circular dependencies using the same issue.