This commit creates a github actions workflow that builds Ruby with the
latest commit of the mmtk-ruby binding and runs `make test-all` with
MMTk enabled.

Several changes were necessary to make this CI pipeline pass:

- C99 prohibits empty compile units, so some code had to be moved around
  in mmtk_support.c to introduce some superfluous #include directives.
  These should either be optimised out or remain unused so have little
  impact on the final binary.

- Correct the dependancy lists in common.mk, by building with the
  appropiate flags defined in `tool/update-deps` and subsequently
  running `make update-deps`

- Pre-fixing all externally visible MMTk related symbols and globals with `rb_`

- Skipping tests related to GC compaction or other functionality
  specific to Ruby's GC.

- Updating YJIT bindings

The native extension is missing a symbol

the result job depends on it

fixes segv in open_ssl/test_ssl.rb test related to ruby assertion that
capacity was sized correctly.

If we use the `excludes-dir` functionality instead of making a method to
skip tests we:

1) get a smaller diff
2) can just skip entire files without needing to include a module
3) don't run into the missing symbol problem caused when checking enabled?
in certain tests

Locally tests can be run like this to skip the problematic tests/files:

```
make -j12 test-all RUBY_TESTOPTS="--excludes-dir=test/.excludes-mmtk" RUN_OPTS="--mmtk --mmtk-plan=StickyImmix" TESTS=test/objspace/test_objspace.rb
```

these need to be in a directory

* The filename was incorrect
* We don't need to skip all of them, only 6 are segfaulting

Without this, nogc won't run at all and is completely broken. It's
required to set a max heap for NoGC.

These tests are testing an implementation detail of Ruby's GC.

The crash reports don't include `+MMTK` in the version string. They
don't for prism or yjit either, but instead of working around it and
"fixing" it in the test, just skip them.

GC compaction isn't supported by mmtk

These are just testing the bug report matches the expected output, not
really worth fixing for this

Object allocation tracing isn't supported in MMTk

Auto compaction isn't implemented in mmtk, we can skip these

ObjectSpace isn't implemented for mmtk

Otherwise we run out of space and it panics trying to do a GC.

Note: I don't think mmtk should try to GC if we run out of space, it
should panic and say ran out of space. It's confusing that it tries to
GC at all.

In MMTK the str_embed_capa is much larger (64) than CRuby (which is 16)
so increase the string size to test mmtk

The other builds have a `working-directory` key, but this one did not.

* Remove diffs that change nothing
* Fix skipped nogc test
* We don't need --mmtk flag if we set the plan, mmtk is turned on
automatically