Support IDs as strings

[Drarig29]

I'd like to use the manager with a MongoDB database and it uses string IDs, so it would be cool to be able to work with strings instead of integers.

[humarkx]

@Drarig29 Any news on this Issue/PR?

[Drarig29]

This was meant to be done for MongoDB and the best approach IMO is this one: #127

MongoDB is a document-based database, whereas the approach of brackets-model is more of a relational approach. So it's best to keep this "relational approach" inside a document which acts as a blackbox.

Instead, you use the brackets-memory-db package to work with a local copy of the document.

So, with all of this, you don't need string IDs anymore.

---

And from a design point of view, this adds a lot of changes in a lot of places, so I prefer not to merge it for now. Unless someone has a good reason to have this feature... do you?

[Drarig29]

Also, supporting IDs as strings would mean that we can't have (string | number)[] and decide whether an item is an ID or a name based on the type in a seeding input.

Related: #148

[laukaichung]

I'm using years (2014, 2018, 2022 etc) as the tournament ID of each annual tournament, so numeral ID is good for my use case.

[Drarig29]

Released in v1.6.0