[4.x] Enable pro fix and improvements

[jesseleite]

When working on the php please multisite command for #9632, I realized that Statamic::enablePro() updates the editions config, but #9435 introduced smarter logic to enable Statamic Pro using an .env var.

What's changed?

If you have the newer editions config style with proper reference to the .env var, nothing has changed:

If it detects that your editions config is not properly referencing the .env var, it'll suggest the --update-config option:

When running with --update-config, it'll update both your .env var and your editions config:

And if it fails to update your editions config, you'll be given instructions on how to manually update this yourself:

Note: I don't think the --update-config should be default behaviour, because the only reason you'd run with --update-config is for older apps where you want to migrate your editions config if it happens to still have a hardcoded boolean. As you can see above though, it's still user-friendly despite being opt-in.

Why these changes?

1. Better UX for the pro:enable command.
2. With this new --update-config option, the Statamic::enablePro() command can now programatically enable pro without any user intervention, but simply deferring to the command.
   • Technically, Statamic::enablePro() is completely broken on newer installs, because it doesn't touch the .env. This PR fixes all that 👍