Add registry mirror config to jib-core API and Jib global config

[chanseokoh]

Towards #1396.

• Jib Core
  • Adds Containerizer.withRegistryMirrors(...) to the jib-core API.
• Jib Maven/Gradle plugins
  • Adds the property registryMirrors to the global Jib config.
  • Also see Add doc for global Jib configuration #3002 for the proposed public doc change.

{
  "disableUpdateCheck": false,
  "registryMirrors": [
    {
      "registry": "registry-1.docker.io",
      "mirrors": ["mirror.gcr.io", "localhost:5000"]
    },
    {
      "registry": "quay.io",
      "mirrors": ["private-mirror.test.com"]
    }
  ]
}

[chanseokoh]

This is ready for review. I'm curious what you feel about storing and returning a map and handling errors in this way.

[loosebazooka]

description or bug?

[chanseokoh]

Sorry, updated the doc. Just realized I forget updating the jib-core CHANGELOG. Will update soon.

[chanseokoh]

I forget updating the jib-core CHANGELOG. Will update soon.

Nah, I will update CHANGELOG once the registry mirror feature is fully working.

[loosebazooka]

Maybe I got here late, but generally I think we use the style of abstract/interface for method inputs and return types? So ListMultimap is the type we expose and ImmutableListMultimap is an impl detail?

[loosebazooka]

I think this looks good to me

[mpeddada1]

Maybe I got here late, but generally I think we use the style of abstract/interface for method inputs and return types? So ListMultimap is the type we expose and ImmutableListMultimap is an impl detail?

Ah right, thanks for clarifying! In that case I don't think my comments apply here. Sorry about that.