Introduce new base & memory storage clients

[vdusek]

New interface of the BaseStorageClient

• Propose & implement a new BaseStorageClient.
• It should introduce a new interface, which does not have to be dependent on the ApifyStorageClient. Instead, we should implement an adapter for it.
• The MemoryStorageClient should implement this interface.

The issues with the current MemoryStorageClient

• fix!: Refactor service usage to rely on service_locator #691 (comment)
  • it should accept just some smaller part of Configuration in the open_storage
• How to economize on RAM when starting a crawl with a large list of urls? #816
  • there are problems with disk offloading
• Improve storage manager and merge it with creation_management module #147
  • there are problems with initialization
• There is probably no need to keep track of an id for each resource client - the memory storage deals with names only. However, we should consider that we will need to support some kind of an equivalent of Apify's non-default, unnamed storages.

[janbuchar]

Regarding that comment on #691, I think that just a Protocol with select properties should do it.

[vdusek]

After further discussions we're gonna:

• Remove collection clients.
• Get rid of the creation_management module as possible it would be.
• Get rid of client methods that do not make sense.
• Update the internals of FE storages.