feat: ParsePositional::non_strict

[ozwaldorf]

Attempt to resolve #373 by adding ParsePositional::non_strict, the inverse of ParsePositional::strict. Derive support also added. Internally adds an enum for the position states; Unrestricted, Strict, and NonStrict.

Tested manually against lutgen, as well as some unit tests, and is a working as expected.

---

Note: There are some failing unrelated unit tests when using --all, but main also has the same failures, so I'll ignore. CI doesn't seem to run them either

[pacak]

There is a small edge case where both strict and not_strict are able to be used together

I think it can be an enum with 3 states: Strict, NonStrict and Unrestricted.

Going to sleep for now, dealing with a newborn is like two full time jobs. Will check tomorrow.

[ozwaldorf]

Refactored the conditionals into a marker trait, in order to only implement the strict/non_strict modifier methods for the default unrestricted parser type. I know it's not the enum, but this way prevents misusage at the type level.

Trying to use both of the modifiers results in a compilation error for manual usage:

As well as derive usage:

[pacak]

Derive macro part looks good, but I'm not sure if it's worth extra complexity to go type level stuff. Can we go back to having a simple enum field and changing runtime behavior based on that?

[ozwaldorf]

Derive macro part looks good, but I'm not sure if it's worth extra complexity to go type level stuff. Can we go back to having a simple enum field and changing runtime behavior based on that?

Sure, it's your call, maintainability is important 👍