Fix incorrect handling of admin_email and actual admin user's email when original admin_email user was deleted

[felixarntz]

Summary

Fixes #601

Relevant technical choices

• This PR ensures the admin_email option and the admin user's email keep their original values even in case they were different (e.g. when the original admin user was deleted).
• See SQLite module: Wrong user details #601 (comment) for additional context on the fix.
• The PR includes one additional (somewhat unrelated) safe guard of not running the automatic setup in a multisite. While it would be great to eventually cover that too, it is a lot more complicated; for now it's the safest option to let the user handle it for a multisite environment.

Checklist

• PR has either [Focus] or Infrastructure label.
• PR has a [Type] label.
• PR has a milestone or the no milestone label.

[aristath]

Should we also add a check for is_multisite in the can-load.php file? 🤔

[mukeshpanchal27]

If we add the is_multisite check in the can-load.php file, we don't need to add it to the activate.php file. WDYT?

[ankitrox]

Yes, I think this is better candidate to go in can-load.php as if site is multisite, then we should instruct not to load module at all rather than instructing to load module and then simply doing nothing!

[felixarntz]

@aristath @mukeshpanchal27 @ankitrox This shouldn't be necessary. It's not that the entire module doesn't work on multisite, it's just that the automatic installation doesn't work with multisite.

[mukeshpanchal27]

Thanks @felixarntz The PR resolved the user email issue, but it still did not pull user details such as first name, last name, website, biographical information, and so on.

Can we fix this edge case issue in the next release? WDYT?

[ankitrox]

Apart from this comment, everything else looks fine to me.

[aristath]

I'll go ahead and pre-approve this. Moving the is_multisite check to can-load is not a deal-breaker, I'm happy to merge this one as-is if we don't want to move the multisite check. cc @felixarntz

[felixarntz]

@mukeshpanchal27

The PR resolved the user email issue, but it still did not pull user details such as first name, last name, website, biographical information, and so on.

I think that's expected. We explicitly say that this setup is not a migration of data, we only set up the bare minimum WordPress SQLite database based on the data from the original database. User details like those you're saying are not essential to a WordPress install (i.e. they are not encompassed by wp_install()).

[dianatupas]

This bug is still existing