[FEATURE] Get well plan for the Github CI pipeline

[andy-k-improving]

Is your feature request related to a problem?

At the moment, the CI build for the project is broken, and PR patch being merged regardless of the CI build result.
This brings additional risk to the project, because there may be additional failure that a particular patch introduced, but being ignored by both Dev and reviewer, due to the fact that build is always failing on the main branch.

What solution would you like?
A clear and concise description of what you want to happen.
There will be three steps process on this ticket:

Phase - 1:

• Temporarily reduce the code coverage to 94%, in order to have passing code coverage test.
• Investigate recurrent build failures on bwc-tests, pages build and deployment / build(dynamic)

Phase - 2:

• Update Github repo setting to only merge PR patch with a succeeded CI build, PR patch with CI failure should be rejected.

Phase -3:

• To gradually build up the coverage back to 99% and resume the code coverage 99% check again.

What alternatives have you considered?
N/A

Do you have any additional context?

[YANG-DB]

Thanks @andy-k-improving - it sounds like we have a plan !!

[andy-k-improving]

Seems to be related: actions/checkout#1590, actions/checkout#1809
Tracing the commit history to better understand since when we have this on main

[andy-k-improving]

The error seems to happen after 8b2d01e, but I don't think it's related to the code change itself, it's more about aciton/checkout@v3 looking for an old version of node which is not exist on the ci-runner.

[andy-k-improving]

Similar fix applied on Job-scheduler and it's working.
I will create a PR to replicate the change tomorrow.
opensearch-project/job-scheduler#702