feat(drag-drop): cdkConnectedTo finds all drop lists with the same ID, instead of only one

#### Feature Description

`CdkDropList` has `id` and `cdkConnectedTo` input properties to allow specifying an id or array of ids for which the drop lists should be connected.

The `id` input property "needs" to be unique, or better put is "assumed" to be unique - meaning when searching through drop lists to connect to by id, only the first match is returned.

Can the "need" for unique ids be removed and change the connected drop list logic to return **all** drop lists with a matching id?

From the user's perspective:

- If I want a drop list to inherently be standalone, provide a unique id.
- If I want a drop list to inherently be connected to others, provide a shared id.

#### Use Case

Connecting drop lists created dynamically, possibly defined in separate template files and with arbitrary DOM relation, **without** the overhead of having to maintain a separate list of all drop lists that should be connected, and making sure this list is properly updated and propagated to each drop list via change detection.

Instead a statically defined (or could be dynamic) id for the `id` and `cdkConnectedTo` inputs will automatically connect all the drop lists without any further coordination from the user.

Similar to what @sroettering mentioned [here](https://github.com/angular/components/pull/13754#issuecomment-436694651), but I don't think a new input property is necessary.

Commencez par localiser l’implémentation de CdkDropList et ses tests, puis suivez la manière dont id et cdkConnectedTo résolvent les listes de dépôt connectées. Mettez à jour le comportement afin qu’un id partagé résolve toutes les listes correspondantes, et vérifiez que les ids uniques restent autonomes tandis que les ids partagés connectent toutes les listes correspondantes.

Rédigé par le modèle d'indexation à partir du texte de l'issue.