Fix conflicting keys on dynamic zone

[Freyb]

As was described in #28 if multiple components share the same attribute name in a dynamic zone, components that are higher on the component list might not get their attributes populated.

Strapi provides two way to populate dynamic zones. As described by the docs:

When populating dynamic zones, you can choose between:

• a shared population strategy, applying a unique behavior for all the dynamic zone's components
• or a detailed population strategy, defining per-component populate queries using the on property.

https://docs.strapi.io/dev-docs/api/rest/populate-select#components--dynamic-zones

This PR fixes this issue by utilizing the on keyword in dynamic components

[Levy-from-Odessa]

Great fix, Thanks
@Barelydead could you merge it, pls?

[Freyb]

@Barelydead Could you check it and merge it?