Update to fix defines that collide with other commonly used defines.

[suicvne]

Recently I experienced the #define's for log levels very badly conflicted with a library I was trying to port. Essentially, by defining them as such, it broke macros that had the words DEBUG or ERROR or INFO on them.

The fix is to re-define the log levels with the library as a prefix.

#define NONE 0
#define INFO 1
#define ERROR 2
#define DEBUG 3	

becomes

#define DBGNET_NONE 0
#define DBGNET_INFO 1
#define DBGNET_ERROR 2
#define DBGNET_DEBUG 3

This is important, the errors that are generated by these macros conflicting are vague and non-descript. Not to mention this library is bundled with VITASDK!