Since the operand of double splat (`**`) may not be a hash, simple
assertion (previous code since d42a64ea) was not enough for this case.

Avoid direct access to error messages as instance variables

- Fix limit handling that fails 15 arguments method calls.
- Fix too early argument packing in arrays.

Make `Array#*` the CRuby compatible behavior when giving a string argument

pre-commit autoupdate

That can create unnecessary arrays when more than 12 arguments are
given to a method.

When `[]=` access includes keyword arguments.

That means when `limit` is `0` it should always generate a hash.

## Summary

This following is a behavior from CRuby 1.8.7 to 3.1.0.

```console
% ruby -ve "p ['a', 'b', 'c']*''"
ruby 1.8.7 (2013-12-22 patchlevel 375) [i686-darwin13.0.2]
"abc"

% ruby -ve "p ['a', 'b', 'c']*''"
ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [x86_64-darwin19]
"abc"
```

### Before (mruby 3.0.0)

mruby unexpectedly gives the TypeError.

```ruby
['a', 'b', 'c']*'' #=> String cannot be converted to Integer (TypeError)
```

### After

This PR makes mruby behave compatible with CRuby.

```ruby
['a', 'b', 'c']*'' #=> 'abc'
```

As far as I checked, the behavior is unspecified when `Array#*`'s argument
is not an instance of Integer class in X 3017 : 2013 (ISO/IEC 30170 : 2012).

## Additional Information

I noticed this difference by the following idiom when writing ASCII art code
using Ruby.

```ruby
%w(foo bar baz)*''
```

e.g. TRICK (https://github.com/tric)

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

Support `disable_presym` for `mrbgems/mruby-errno`

Support `MRB_NO_STDIO` for `mrbgems/mruby-errno`

We used to check them by `mrb_ensure_xxx_type()` functions, but type
errors there should not occur if there's no bug in code generations.
So we use assertion rather than dynamic type checks.

Not the libraries loaded by `-r`. Instead, `.mrb` extension in the path
should determine whether they are compiled binary.

Pinning the Visual Studio version in GitHub Actions

The `mrbgems/mruby-errno/src/known_errors_def.cstub` file has been extended, so the `mrbgems/mruby-errno/src/known_errors_e2c.cstub` file is no longer needed.

ref. #2485

The `SystemCallError#to_s` method also needed to be modified, but since it has no functional difference from the `Exception#to_s` method, it will be removed.

Until now, `windows-latest` meant `windows-2019`, but now it seems that it is being replaced by `windows-2022` in stages.
At the same time, Visual Studio 2019 will be replaced by Visual Studio 2022.

Since mruby's CI is configured to assume Visual Studio 2019, we'll update this and explicitly specify `windows-2022`.

Check the type of the keyword rest argument

If a non-hash object is passed in `OP_SEND` and `OP_SUPER`, an error should occur.

```ruby
kwd = "string"
p(**kwd)  #  => expect raised TypeError
```

`(irep->pool[b].tt & IREP_TT_NFLAG) == 0` is always true ensured by
the assertion.

Updated mruby-errno/README.md to pass the lint checks.