Incompatible with PrestaShop 9.x

[acolombier]

Prerequisites

• I understand and accept the project's code of conduct.
• I have already searched in existing issues and found no previous report of this bug.

Describe the bug and add attachments

It looks like it is not possible to consult customer data and complete an erasure procedure in version 9.x. The stack trace is

Symfony\Component\ErrorHandler\Error\UndefinedMethodError:
Attempted to call an undefined method named "ajaxDie" of class "AdminAjaxPsgdprController".

  at modules/psgdpr/controllers/admin/AdminAjaxPsgdprController.php:92
  at AdminAjaxPsgdprController->ajaxProcessGetCustomerData()
     (classes/controller/AdminController.php:976)
  at AdminControllerCore->postProcess()
     (src/PrestaShopBundle/Controller/Admin/LegacyController.php:81)
  at PrestaShopBundle\Controller\Admin\LegacyController->legacyPageAction(object(Request))
     (vendor/symfony/http-kernel/HttpKernel.php:181)
  at Symfony\Component\HttpKernel\HttpKernel->handleRaw(object(Request), 1)
     (vendor/symfony/http-kernel/HttpKernel.php:76)
  at Symfony\Component\HttpKernel\HttpKernel->handle(object(Request), 1, true)
     (vendor/symfony/http-kernel/Kernel.php:208)
  at Symfony\Component\HttpKernel\Kernel->handle(object(Request), 1, true)
     (admin662nx1jmtgau3xzskao/index.php:72)                

Looking at the changelog, it would seem ajaxDie was only available in version before 9.x

Steps to reproduce

1. Install the latest PrestaShop (9.1.4 in my case)
2. Install the GDPR plugin
3. Try to view or erase customer's personal data

Expected behavior

The data should display or the erasure complete, and not 500 response should be noticed

Actual Result

An empty rectangle displaying and a 500 XHR response with the linked stack trace is visible in debug console

PrestaShop version where the bug happens

9.1.4

Module version where the bug happens

1.4.3

PHP version(s) where the bug happened

8.0

Your company or customer's name goes here (if applicable).

No response

[acolombier]

Ah I realised the latest release in Github is actually not the latest release available (2.0.1 is out). However, I am now getting other traceback, so it would suggest that there may still be compatibility issue I suppose?