Prefer addSql() over executeStatement() in migrations

executeStatement() doesn't work well in migrations; for example it
doesn't respect the --dry-run option.

In Version20210407120356.php it's not possible to use addSql(),
because the statements use the results of previous statements. This
commit changes that file to use *only* executeStatement() for
consistency.

Also remove an unused import.

webapp/migrations/Version20210407120356.php

@@ -66,7 +66,7 @@ public function up(Schema $schema) : void
                 );
             }
 
-            $this->addSql('ALTER TABLE `executable` DROP COLUMN `zipfile`');
+            $this->connection->executeStatement('ALTER TABLE `executable` DROP COLUMN `zipfile`');
         }
     }
 

webapp/migrations/Version20230508163415.php

@@ -4,7 +4,6 @@
 
 namespace DoctrineMigrations;
 
-use App\Entity\ExecutableFile;
 use Doctrine\DBAL\Schema\Schema;
 use Doctrine\Migrations\AbstractMigration;
 
@@ -32,7 +31,7 @@ public function up(Schema $schema): void
                     )
                 )
             );
-            $this->connection->executeQuery('UPDATE immutable_executable SET hash = :hash WHERE immutable_execid = :id', [
+            $this->addSql('UPDATE immutable_executable SET hash = :hash WHERE immutable_execid = :id', [
                 'hash' => $newHash,
                 'id' => $immutableExecutable['immutable_execid'],
             ]);

webapp/migrations/Version20231120225210.php

@@ -34,7 +34,7 @@ public function up(Schema $schema): void
 
             if ($updated) {
                 $newExtensionsJson = json_encode($extensions);
-                $this->connection->executeQuery('UPDATE language SET extensions = :extensions WHERE langid = :langid', [
+                $this->addSql('UPDATE language SET extensions = :extensions WHERE langid = :langid', [
                     'extensions' => $newExtensionsJson,
                     'langid' => $language['langid'],
                 ]);