```ruby
p ((while true; p 1; break; end))
```

should print `1 nil` but was `1`.

pre-commit autoupdate

https://pre-commit.com/#pre-commit-autoupdate

Also, now too big capture group index just gives `nil`, not error.

- stdlib.h
- stddef.h
- stdint.h
- stdarg.h
- limits.h
- float.h

build(deps): bump github/super-linter from 4.5.0 to 4.5.1

Bumps [github/super-linter](https://github.com/github/super-linter) from 4.5.0 to 4.5.1.
- [Release notes](https://github.com/github/super-linter/releases)
- [Commits](https://github.com/github/super-linter/compare/v4.5.0...v4.5.1)

---
updated-dependencies:
- dependency-name: github/super-linter
  dependency-type: direct:production
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

`OP_LOADI Rn -0` should be `OP_LOADI_0`.

This is preparation for integer constant folding.

Explicit write barrier for binding

Output an error if the `INTPTR_MAX` macro is undefined in C++

Avoid implicit casting from void pointers for C++

When doing `conf.enable_cxx_abi` and compiling with FreeBSD + clang or MinGW, such as `INTPTR_MAX` constant macro is not defined if `#include <stdint.h>` precedes `#include <mruby.h>`.
Currently I get a warning when I use an undefined macro, but if I don't notice it I get confused in a link error.
It can be expected that the problem will be easier to understand by making a clear error.

Adding `-Werror=undef` as a compiler flag can also result in an error, but this can be a problem if the system header file itself uses undefined macros, for example.
This patch does minimal confirmation only, but has no side effects.