Thanks for your updates.
If those tables were corrupted then there could be other database corruption. You might be better exporting your layouts from your 1.8.2 CMS and importing them in to a new 3.x CMS instead.
If you want to press ahead regardless, you’ll need to recreate those tables - they can’t just be removed I’m afraid. So you’d need to restore your v1.8 CMS backup, repair or recreate those tables, and then upgrade. If you have to recreate then I don’t think it will ever upgrade properly as phinx requires the data in that table to manage the upgrade, so you should try and repair it first.
The logs there also suggest you’re trying to run MySQL 5.7 with a MySQL 5.6 data file. You need to ensure you’re running MySQL 5.6 until you have completed the upgrade to 2.3.16, and then you can switch to MySQL 5.7. It is not supported prior to that.
Once you have switched, you’ll need to manually run the mysql_upgrade command - details here: