Adapt to Apify's "multiple storages" functionality

[janbuchar]

This is a feature that should complement the unnamed non-default storages:

1. Apify passes a JSON object with additional storage IDs to the Actor via environment - ACTOR_STORAGE_IDS - we should add this to the Configuration class. It is an object with three properties - datasets, keyValueStores and requestQueues. Each of these properties contains a name -> ID dictionary.
2. We should extend the AliasResolver class to utilize this so that Dataset.open(alias="additional-dataset") just works (™️). If an unknown alias is requested, we can either fall back to the current logic (create it, put an ID into the default KV-store) or shout at the user.

See https://apify.slack.com/archives/C07ED56TA1K/p1770217755895989