Clean USVFS namespace

[Holt59]

• Remove deprecated functions.
• Prefix all exposed USVFS function as usvfsXXX.

[Al12rs]

What is the reason for prefixing the public functions with usvfs?
I assume it helped for debugging or what specifically?

Mostly ask for posterity

[Twinki14]

It makes sense from my perspective seeing that usvfs is first and foremost a library with many public functions, the prefix would:

• Help distinguish library-specific calls vs whatever runtime is using the library at a glance
• Keep usvfs from limiting certain function method names, eg now I could implement a ClearVirtualMappings in my app that uses usvfsClearVirtualMappings inside it (I'm sure you could still do that with macro-fu, but the prefix makes it easier)
• Help contributing developers distinguish what's public and what's internal in usvfs at glance

In my view the biggest benefit to the prefix is an overall way cleaner library, to both work on and consume

[Holt59]

What is the reason for prefixing the public functions with usvfs? I assume it helped for debugging or what specifically?

Mostly ask for posterity

As @Twinki14 said It's just to have something cleaner and more consistent:

• since all methods are declared in the global namespace, the usvfs prefix avoid clash issues and makes it clear were the method comes from - from some methods such as ClearVirtualMapping, it is kind of obvious based on context, but for others it is not (at least for me), e.g., GetLogMessages, PrintDebugInfo or CreateProcessHooked,
• there were some discrepancies between methods since some used usvfs prefix (e.g., usvfsConnect), so this fixes it.