keep code coverage status for job that is not run in a pipeline.
Problem to solve
The status of coverage report badge for a job will become "unknown" if the associated job is not run in the latest pipeline. this is troublesome, usually we don't want to run every job in a pipeline, can we make the coverage badge status persistent from the job's last run if nothing new is available in the latest pipeline?
Running every job each time can slow down the pipeline a lot.
Keep the coverage status for a job from last successful pipeline if the associated job is not created for the new pipeline