chore: add lock to jib cache lookup

[ericzzzzzzz]

#7409

Descriptions:

• add lock for jib cache lookup as it will trigger mvn/gradle command to download deps, running those command concurrently can lead errors, the task may use deps which are still in downloading state this will end up skaffold command fail.
• Was thinking different approaches to solve this problem
  • align cache lookup concurrency with build concurrency
    • Not ideal, as for other builders, users may still don't want to limit the concurrency for building
    • Even so, the only option to fix the issue is probably set the concurrency to 1
  • add other flag to control concurrent lookup
    • This seems quite over-engineering and not easy-to-use, users may have to run skaffold command with different arguments from different sessions
• Although, locking this can hurt the performance issue, runs other than the first run should be relative fast as the downloading won't need to happen.

Test Plan

• remove ~/.m2 folder
• the follow the reproducible steps in Skaffold Cloud Builder fails fetching dependencies on first skaffold build when using jib + mvnw #7409