Make VaultMigration compatible with disabled/removed Magento PayPal module (#2806)

* Make VaultMigration compatible with disabled/removed Magento PayPal module

**Issue**
The installation/upgrade of the Adyen Payment plugin fails with the following error:
```
Column not found: 1054 Unknown column 'method_code' in 'where clause', query was: SELECT `paypal_billing_agreement`.* FROM `paypal_billing_agreement` WHERE (method_code = 'adyen_oneclick') AND (status = 'active')
```

**Cause**
The Adyen Payment module re-creates the table during migration by adding the agreement_data field (via db_schema.xml).
However, when attempting to migrate the billing agreements to the vault, the process fails to query the table using
the `method_code` and `status` because these fields do not exist in the table.

**Solution**
Ensure VaultMigration does not fail if the `paypal_billing_agreement` table is missing or required fields are missing.

* Use getTableName() method to obtain the full table name containing table prefix

* Revert "Use getTableName() method to obtain the full table name containing table prefix"

This reverts commit e59cbbc.

* Drop `paypal_billing_agreement.agreement_data` declaration

* Bump MariaDB version

* Use connection to check the existence of the table

---------

Co-authored-by: Fabian Hurnaus <fabian.hurnaus@tractive.com>
Co-authored-by: Can Demiralp <ecandemiralp@gmail.com>
Co-authored-by: Can Demiralp <can.demiralp@adyen.com>

Author: 3 people

.github/docker-compose.yml

@@ -2,7 +2,7 @@ version: '3'
 
 services:
   db:
-    image: mariadb:10.4
+    image: mariadb:11.4
     container_name: mariadb
     networks:
       - backend

Setup/Patch/Data/VaultMigration.php

@@ -56,6 +56,17 @@ public function apply(): void
 
     private function migrateBillingAgreementsToVault(ModuleDataSetupInterface $setup): void
     {
+        if (!$setup->getConnection()->isTableExists('paypal_billing_agreement')) {
+            $this->adyenLogger->addAdyenInfoLog('Table paypal_billing_agreement does not exist, skipping migration');
+            return;
+        }
+
+        $columns = $setup->getConnection()->describeTable('paypal_billing_agreement');
+        if (!isset($columns['method_code']) || !isset($columns['status'])) {
+            $this->adyenLogger->addAdyenInfoLog('Columns method_code and status do not exist, skipping migration');
+            return;
+        }
+
         $paypalTable = $setup->getTable('paypal_billing_agreement');
         $connection = $setup->getConnection();
 

etc/db_schema.xml

@@ -9,9 +9,6 @@
   <table name="sales_order_payment" resource="default">
     <column xsi:type="varchar" name="adyen_psp_reference" nullable="true" length="255" comment="Adyen PspReference of the payment"/>
   </table>
-  <table name="paypal_billing_agreement" resource="default">
-    <column xsi:type="text" name="agreement_data" nullable="true" comment="Agreement Data"/>
-  </table>
   <table name="adyen_order_payment" resource="default" engine="innodb" comment="Adyen Order Payment">
     <column xsi:type="int" name="entity_id" padding="10" unsigned="true" nullable="false" identity="true" comment="Adyen Payment ID"/>
     <column xsi:type="varchar" name="pspreference" nullable="false" length="255" comment="Pspreference"/>