VerifyUserData job always gets readded

[juliushaertl]

In cases the VerifyUserData job fails or terminates immediately (due to no validation being required) the job is instantly readded again due tot he updateAccount logic. It seems that there was some change to fetch the old account data now in an indexed array rather then one with the property names as key. In the following $oldMail will just always be null and the job gets readded:

Steps to reproduce:

• set 'lookup_server' => '', in config.php
• run the cron job runs and is removed due to

  server/apps/settings/lib/BackgroundJobs/VerifyUserData.php

  Line 99 in f49a751

  $jobList->remove($this, $this->argument);

Expected:

• There is no job present anymore after the removal

Actual:

• The job gets added again right away

@blizzz @Pytal As a quick fix i thought about just bringing back the property name array key but I don't feel familiar enough with the code to tell if that is a good idea right away. Maybe you have a better insight there.

Could potentially cause quite some cron delay or unnecessary load on systems with larger user count.

[Pytal]

Account properties were switched from an associative to indexed array to allow for multiple email addresses #27474

Wasn't able to test this as the job wasn't run on my instance after doing the repro steps so let me know if #30491 fixes it @juliushaertl