Feature: Update config to work with new mock models

[Mclilzee]

Checks

• I have thoroughly read and understand The Odin Project Contributing Guide
• The title of this issue follows the command name: brief description of request format, e.g. /help: add optional @user parameter

Do you want to be assigned to this issue?

• I would like to be assigned this issue to work on it

Description of the Feature Request

While working on #793 and updating the new Mock Models, I realized most of the mock models can be filled directly from our config.js file.

The problem is the config.js file is formatted in a way to be easier to work with for some tests. If we format it properly for example each role or channel in the array being
{ id, name } then we can create a default mocks that will auto-inject all of these values directly for our tests without having to manually fill them every time.

If necessary we can add more values to the config so that we can simulate our whole discord server, the only thing that would be missing is members, which we will still have to rely on fake members that we create manually.

Acceptance Criteria

• Reformat config file and refactor all places where its being used.
• Create default mocks for TextChannel, Guild, Roles etc

Additional information

No response

[mao-sz]

Sounds good to me @Mclilzee , thanks

[mao-sz]

Oh, I just noticed you didn't actually check the assignment box. Was this intentional?
If so, would you be able to elaborate on exactly how you imagine the file could be reformatted for this purpose?

[Mclilzee]

Its intentional but not because I don't feel like working on it, but rather because I haven't had much free time lately haha. but if you want me to take care of it I'm more than happy to ;)

For example lets take a look at our Guild mock:

class Guild {
  #roles = new Collection().set(1, { name: 'club-40' });
  #channels = new Collection();

  constructor({channels = [], roles = [] }) {
    channels.forEach((channel) => {
      this.#channels.set(channel.id, channel);
    });

    roles.forEach((role) => {
      this.#roles.set(role.id, role);
    });
  }

If we format the config properly we could just do something like this

const config = require('../../../config');

class Guild {
  #roles = new Collection();
  #channels = new Collection();

  constructor({ channels = config.channels, roles = config.roles }) {
    channels.forEach((channel) => {
      this.#channels.set(channel.id, channel);
    });

    roles.forEach((role) => {
      this.#roles.set(role.id, role);
    });
  }

[Mclilzee]

Or rather we could also inject the mocks directly into the config, so instead of having channels as array, maybe we have them as array of TextChannel mock. Not too sure about that one because now we are coupling together a discord mock like structure and just data.

[mao-sz]

Gotcha. I'll unassign you for now but if you do get the time for it then that's awesome, just let me know here.
There's no rush for this at all since it's just a refactor, so can always revisit this after the image kick stuff and the own database stuff land.

Edit: Very keen on not bringing mocks into the config. The config file should just be data.

[Mclilzee]

@mao-sz Assign this to me please, I got the bandwidth to start tackling this.