feat(Core): Add voice chat implementation.

[heyitsbench]

Changes Proposed:

This PR proposes changes to:

• Core (units, players, creatures, game systems).

Issues Addressed:

• Closes Voice Chat #5063

SOURCE:

The changes have been validated through:

• The changes promoted by this pull request come partially or entirely from another project (cherry-pick).
  • The majority of the implementation has been cherry-picked from a currently open CMaNGOS PR authored by celguar, which itself was based primarily off of the Ascent Team implementation by burlex. It currently requires the use of a separate VoiceChat server, see TODO.

Tests Performed:

This PR has been:

• Tested in-game by the author.
• This pull request requires further testing and may have edge cases to be tested.

How to Test the Changes:

• This pull request requires further testing.

1. Use it.
2. Break it.
3. Prof it.

Known Issues and TODO List:

• Clean up logging everywhere and probably add some here and there.
• Try to fix network stuff.
• Add CMake stuff to fetch and build voice chat server as in CMaNGOS PR. This might be one of the bigger points of contention with this PR, but I'm not sure the best way of dealing with this. I honestly don't think the behavior should be merged into the worldserver (cross-realm one day and all that) and a separate server definitely does seem to be how Blizz handles it, but obviously relying on an external repo for it might not be preferable. Maybe forking by the AC organization would be an option, but again, not sure how maintainers want to approach this one.
• Implement the various commented out functions.
• Fix channels.
• Properly adjust priority when group leader is swapped for applicable channels.

How to Test AzerothCore PRs

When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].

You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:

http://www.azerothcore.org/wiki/How-to-test-a-PR

REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).

For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.

[heyitsbench]

This is very work in progress. Opening now since I've been using the diff to look for things to fix, and it's easier when the PR is up. Plus any interested eyes can get on it and point out issues.

[Tereneckla]

Oh god, he is doing the thing

[LuckyLuc96]

Looks good ready for prod

[blinkysc]

Wow awesome

[TheSCREWEDSoftware]

Hypothetical the usage / implemntation of the voice server would run along the auth and world? for exclusive 1 realm (1 per realm) or all realms? Even if it's a feature that seems under-use even now a days, I think this is a very cool addition.

[heyitsbench]

Not sure how the voice server itself responds to multiple connections, but ideally it would allow multiple to apply to multiple realms. Wouldn't make sense to limit itself to one realm by design, plus would cause problems for a possible cross-realm instance/battleground implementation.