Assigned IDs for products and categories

[asgerjensen]

For product, categories in particular, and maybe other things as well, it would be great if the creator can dictate the ID.

This makes it easier in scenarios where existing services already have assigned a globally known (external) id to the entity.

Example: you are adding medusa to a stack that has an existing recommendation engine in place, that has been using the PIM partnumber as key for a long time. As the PIM is the MDM master, reusing its key, makes it easier for all other systems in the stack to coordinate based on this.

Having the ability to assign the ID means the frontend can directly use retrieve with the record returned from the recommendation system; something that is not possible with the external_id field, even if it /was/ searchable.

Generally, i find, in composable commerce scenarios, that using "global" or "external" IDs make alot of things easier, because it is stable across all service-boundaries, and is much easier to read in the logs and data-grams afterward.

The current IDs are created, not as GUIDs but as ULIDs (if i understand correctly), and this behavior could continue to be so, if the creator does not explicitly set the ID.

[asgerjensen]

PR with implementation #14263