Update outdated V syntax highlighting

[D4MI4NX]

This PR updates the long outdated V syntax highlighting and adds some new features. Changes include:

Detection:

• Add .vsh and .vv filename detection (note: .v is omitted for Verilog)
• Add shebang header detection for VSH files

Highlighting

• Add common C preprocessor directives
• Introduce new reserved language keywords
• Add identifiers for new OS, compiler, platform and compilation options
• Include bit-wise XOR (^) in operators
• Support generics in function definitions and calls
• Update to new @[] attribute syntax
• Improve attribute highlighting
• Add support for conditional compilation
• Add u8 and i32 types to type rule
• Remove non-existent u128 and i128 types from type rule
• Add nil constant
• Fix broken highlighting when escaping a character within backticks (``)
• Add NOTE to todo rule
• Treat shebang as comment

[Andriamanitra]

I think this could be a bit less specific to support additional/different args to both env and v. Maybe something like "^#!\\S*env( .*)? v " ?

[D4MI4NX]

Yes, you are right. Maybe we can agree on ^#!\\S*\\benv(\\s.*)?\\sv\\b?

[Andriamanitra]

That seems reasonable. The v\\b has some potential to cause false positives but they would probably be rare enough. I don't know of any popular tool or language that would use eg. v-something or v=something.