Port as much of ACE as possible to ACE. namespace

[Ally-for-Hire]

Idea

This is a pretty major refactor, continuing on the previous one of internal-function namespaces, this targets the remaining hooks and cvars left from ACF2. We can use AI to identify legacy functions and namespace incompatibilities and monitor the resolution. The scope and implementation of the work was designed by the team itself.

Description

This refactor will finish converting the namespaces to a consistent ACE. and ACE_ rather than the various ACF., ACF_, or ACE_ with very little rhyme or reason found through the code. A previous PR already fixed most of the internal functions, and this one is scoped to finding and resolving all of the rest that won't break backwards compatibility. This will mostly avoid touching player-facing behaviour and shouldn't touch optimization, it will just be the next step towards a better back-end. Previously this was split into the following categories:

• ACF. was used for global ACF2 and older ACE functions
• ACF_ was used for ACF2 and older ACE specific functions
• ACE_ and ACE. were used inconsistently across newer functions

We want to move all ACE functions to the ACE. namespace, and move all hooks to the ACE_ namespace or give them unique hook IDs so they can't get overwritten or become incompatible trivially. We can also take this time to ensure all the code follows CFC's GLUA guidelines.

Notes

• This will not touch E2/SF libraries, and that will likely remain the last permanent blocker between ACF3 and ACE compatibility even after the class rework and entity migration.
• Major compatibility functions and hooks will be left alone for now, with bridges or aliases left if we do touch them.

[Ally-for-Hire]

holy git diff 😭 , not much i can do about it without reverting functionality. what it does really does just touch SO many files and functions

[KemGus]

Waiting for this to be adressed:

[Ally-for-Hire]

that was addressed and fixed