feat(vote): relative time remaining + embed

[sudojunior]

closes #26

• Remaining time is tracked internally within the command execution scope itself

  While the notation of <t:{round(timeMs/1000)}:R> can be used, there is still significant latency within the second it is due to expire. This may be due to network latency on local testing, or natural latency when Discord communicates with the host machine (or vice-versa in response).

• Vote mockup now has an embed which uses the randomly provided game color and title

https://user-images.githubusercontent.com/8607699/174449942-9f340610-331c-4dc8-9b82-5e7e0ad2ffd6.mp4

[sudojunior]

bda403e is part of this PR, it just got committed directly to main as I didn't select a branch to edit from... 😐

[sudojunior]

Additional change: If all or majority (with alive player count of 5 or more), end the voting timeout - which would require the class structure proposed further up.

• [x] Record time delay between calling the method and resolving the promise.
• [ ] Optional timeout as a rejection

class BallotInstance extends EventEmitter {
  waitFor (event: string): Promise<number> {
    const start = Date.now();
    return new Promise((resolve, reject) => {
      this.once(event, () => resolve(Date.now() - start));
    });
  }
}

[sudojunior]

Additional change on majority

This would be better implemented as a game option (endOnMajority) rather than forcing the flow of a game based on the global configuration or hard coded logic. With the inclusion of an early majority (games are expected to be faster and players may have less time to submit their vote - regardless if the given majority decides unanimously or not).