Refactor supported registered as providers

currently `Registry` class contains a lot of logic related to specific registry: Amazon, Google etc.

it gets hard to handle all the specifics of registries in one class.

Implement "provider" approach for well-known registries based on common interface/base class. Customization points:
- supporting parallel upload
- supporting chunked upload
- size of the chunk
- auth specifics
- provider-specific guidance/options for fixing auth

Start by reading the Registry class and inventory its Amazon- and Google-specific logic. Trace how upload, chunking, authentication, and guidance options are currently selected. Done means well-known registries are handled through a common provider interface with the listed customization points, without keeping their specifics centralized in Registry.

Written by the indexing model from the issue text.