[Draft] Sorted partition ids alphabetically in EventStore

[JBBianchi]

Important note:
This fix only applies to fresh installs.
For people with an existing setup, they either need to drop their EventStore volume or edit/reset the partitions:

• cloud-events-partition-ids-BySource
• cloud-events-partition-ids-BySubject
• cloud-events-partition-ids-ByType

by adding stream.sort();

fromStream('cloud-events')
    .when({
        $init: () => [],
        $any: (stream, evt) => {
            if (!evt || !evt.metadataRaw || !evt.metadataRaw) return;
            const metadata = JSON.parse(evt.metadataRaw);
            const id = metadata.##propertyName##;
            if (!id || stream.includes(id)) return;
            stream.push(id);
+           stream.sort();
        }
    });

Closes #20

[cdavernas]

Cant run it here, but isn't your example just gonna push the event to the "cloud-event" stream (ie. stream), then ordering it? This is obviously not the expected behavior

[cdavernas]

Can you fix the warnings in Store? You need to either to a null check, or add an exclamation mark at the end of line 278

[JBBianchi]

Cant run it here, but isn't your example just gonna push the event to the "cloud-event" stream (ie. stream), then ordering it? This is obviously not the expected behavior

Not sure to understand what you mean. It's the same projection than before except now, the partition content is sorted each time its modified instead of just being modified. Does that make sense ?

[JBBianchi]

This PR raises a concern:

Should we reorder the ids in the ES projection or only when read/required.

If it's sorted directly in the projection, then we loose a piece of information: the order the partition were created. For instance, it won't be possible to get the 10 last created subjects.

If not, then it means "computing" for each read which adds a little overhead.