The state of Whateverable (2023 server migration)

As I'm moving to the new server, I'm trying to dockerize everything that I had and migrate it. Whateverable is one of the projects. Note that for now I'll keep hosting it (I think I've been doing a good job at that throughout the years), but once dockerized, the bots can be moved to Raku infrastructure if needed.

The work turned out to be more difficult than I expected do to several regressions or changes in Rakudo that resulted in bitrot. This is a ticket to document the progress and the obstacles.

• ⚠️ Bots work in general, but there are issues with GLIBC
• Bisectable – seems to work
• Committable – seems to work
• Benchable
• Evalable
• Statisfiable
• Unicodable – runs and works fine, or so it seems. Haven't tested all the functionality yet.
• Bloatable
• Quotable
• Greppable
• Coverable
• Releasable
• Nativecallable
• Squashable – 🪦 This bot has been offline for quite some time, for the time being it's not going to be revived. It was used for squashathons, but as far as I know it's no longer a thing
• Reportable
• Notable – needed a workaround for “Invocant of method 'match' must be a type object of type 'Any'”
• Shareable
• Undersightable – 🪦 This bot has been offline for quite some time, for the time being it's not going to be revived.
• Tellable – needed a workaround for “Invocant of method 'match' must be a type object of type 'Any'”
• Sourceable – needed a workaround for “Invocant of method 'match' must be a type object of type 'Any'”
• Linkable – Seems to work
• Buildable – this is a new bot that is probably needed to keep running the build script and to expose the status.

Start by reviewing the Docker migration status and the checklist of Whateverable bots in the issue, paying attention to the reported GLIBC and Rakudo regressions. Done means the remaining intended bots are migrated and their obstacles or workarounds are documented; the issue does not name specific files or tests.