`a *= b != c ? d : e;` is parsed incorrectly as a result

This reverts commit eb6649e0c2.

Previously, pointers were associated with the function identifier, now they're associated with the return type

This resolves conflicts with declarations that can be interpreted as binary_expressions

* feat: allow identifiers in string concatenations

Resolves errors in strings of the form:

   ("failed in line %" PRIdLINENR)

---------

Co-authored-by: Lewis Russell <lewis6991@gmail.com>

_Generic is a C11 feature, __restrict__ and _Noreturn were added to type_qualifiers

It's allowed in gcc and clang

According to cppreference, identifiers are `(XID_Start | '_')
XID_Continue*`, which is the case as of C++23 and C2x. I have confirmed
this myself with the drafts of C++23 and C2x.

https://en.cppreference.com/w/cpp/language/identifiers

Clang indeed implements identifiers as `(XID_Start | '_') XID_Continue*`
in C++ mode and C2x mode, with a slight extension to the character set
to include some extra math characters:
231992d9b8/clang/lib/Lex/Lexer.cpp (L1517-L1530)

This also lets it bind to _any_ statement, which is necessary for some
c++ attributes that can attach to the statement in if, while, and
do/while statements.

* Add support for C23 attributes

https://en.cppreference.com/w/c/language/attributes

* Use wrapper for statements with attributes to reduce state machine size

* Missed a couple _declarators that needed attributes directly after

* Use annotated_declarator for declarators that have attributes immediately following them

* Give field and type declarators the same attribute treatment

* Add support for Microsoft-specific modifiers

Microsoft-specific modifiers are keywords can be used to modify declarators to form derived types.

The specification for the modifiers themselves is here:
https://docs.microsoft.com/en-us/cpp/cpp/microsoft-specific-modifiers?view=vs-2019

* 0.16.1

* Add a rule for left part of assignment: it'll be helpful to add scoped_name_identifier (c++)

* Inline the assignment_left_expression rule

* #include can be followed by a macro name or a macro call

* In preproc_include, use preproc_call_expression

* Parse expressions in preprocessor #if statement

* Make preproc_expression look like a normal expression

* Hide the wrapper rules
* Alias the rulres to match their corresponding expression rule
* Handle line continuations as extra tokens

Fixes #32

Fixes #31

* Fix multi-statements in for initializer and update parts

* Finally the bug was only in the initializer part

* Fix error with ++L (consequence of support for L strings)

* Update to tree-sitter 0.15.5

Fixes #24