Execute standalone setup:upgrade for sample data to trigger activation

[markshust]

Fixes #1401

[what-the-diff]

PR Summary

• Activation of Sample Data Post-Deployment
  The updated process now includes a step where setup:upgrade runs to activate the sample data right after it's been deployed. This enhancement ensures the new sample data is live and ready for use promptly.

• Two-Factor Authentication (2FA) Modification
  The message prompting the disabling of the Two-Factor Authentication feature has been altered. Instead, users are now directed towards installing a module called DisableTwoFactorAuth. This can be particularly helpful in a development environment where 2FA may disrupt work.

• Removal of Redundant Upgrade Setup
  The command that triggers setup:upgrade after enabling the new module is deleted. This is primarily due to its redundancy, considering the same command is already run during the deployment process.

• Swap of Final Optimizations with Cache Flush
  The finalization process has been updated to replace the previous version's optimizations with a cache flush. The change ensures that all system updates are immediately applied, reflecting recent modifications in an expedient manner.