To support CI job on riscv64 self hosted runner

[yuzibo]

No description provided.

[yuzibo]

To address the issue.

I left some comments on there, please review it also

[yuzibo]

I hope these sed usages can be accepted in order to speed up the whole workflow. And this clearly demonstrates what we did.

[tgross35]

Is the speed difference that significant? I'd rather not use the mirrors if possible to reduce the possible points of failure or things that could get out of sync.

[yuzibo]

Yes, this is one of the feasible solutions we can implement.

On the self-hosted riscv64 runners, outbound access to some upstream services can be intermittently unstable due to external network factors, which may occasionally affect CI reliability before the actual build or tests start from my experimental. In fact,localized mirror services were included as an initial goal of this project to ensure the stability of CI.

Regarding the risk of mirrors getting out of sync: these mirrors are actively maintained and have a daily synchronization mechanism to track upstream changes, along with basic health checks to ensure they remain usable. This helps reduce the risk of silent divergence.

We do not publish our mirror service in case other users abuse it to affect the stability of our CI, if necessary, we can publish it after our internal assessment.

Using these Prepare mirrored sources with sed is a more transparent approach than using a cached solution, which increases complexity. But for r-l/r, we have to depend on lots of cache strategy, If we get to that point.