[Tools, py] Fix announce.py and adds native announce command from tools directory

[texastoastt]

I affirm:

• I understand that if I do not agree to the following points by completing the checkboxes my PR will be ignored.
• I understand I should leave resolving conversations to the LandSandBoat team so that reviewers won't miss what was said.
• I have read and understood the Contributing Guide and the Code of Conduct.
• I have tested my code and the things my code has changed since the last commit in the PR and will test after any later commits.

What does this pull request do?

Restores the expected behavior of announce.py by sending a system message to all players in all zones. Due to changes in messageType, announce.cpp and accompanying CMakeupdates required to build the new native executable. announce.py was also update for backward compatibility to call the new native exe.

Steps to test these changes

From the server/tools/ directory, use either ./announce "TEST MESSAGE" or python3 announce.py "TEST MESSAGE" to confirm message sent in-game.

[zach2good]

This is much more complex than it needs to be. You only need to update the layout of the message produced by the existing python script and it'll start working again. You can see the new layout in ipc_stubs, I believe, or somewhere near there.

[zach2good]

struct ChatMessageServerMessage
{
    uint32            senderId{};
    std::string       senderName{};
    std::string       message{};
    uint16            zoneId{};
    uint8             gmLevel{};
    CHAT_MESSAGE_TYPE messageType{ MESSAGE_SYSTEM_1 };
    bool              skipSender{};
};

struct ChatMessageCustom
{
    uint32            recipientId{};
    std::string       senderName{};
    std::string       message{};
    CHAT_MESSAGE_TYPE messageType{};
};

[texastoastt]

I ran into some alpaca issues trying to update the existing script but with what you just sent, I think I know why. Not sure how I missed that when I went digging. Going to make another pass at this with that info.

[texastoastt]

Ok got it sorted as a python standalone and removed the previous stuff that ultimately isn't needed anymore. I absolutely over-complicated trying to understand the alpaca encoding which took me down the wrong rabbit hole previously.

[zach2good]

This is now giving conflicting information with 2 lines below

[texastoastt]

Yep, sorry. That's an artifact from my troubleshooting.

[zach2good]

Why is this utf-8, we aren't using that in the C++ side?

[texastoastt]

This is my misunderstanding, as i see utf-8 in the db and other places. What character set do i need to use for this specifically, and I'm happy to adjust.

[zach2good]

Comment is redundant, it's already called socket.ntohl

[zach2good]

(network to host long)

[texastoastt]

You're right. Will fix that.