Improve MxCloud activity overview

Currently, the Cloud Activity log only shows deployment, backup, and permission activities performed on an environment. This leaves a gap for developers and administrators who need full visibility into what is happening on their environments.

It would be nice if the following activity types can be added to this log:

• Automatic restarts – e.g. restarts triggered by the platform itself (not initiated by a user), so it's clear whether downtime was caused by an action or happened automatically. Restarts by support included.
• Maintenance activities – planned or unplanned maintenance performed by Mendix on the underlying infrastructure, so teams aren't left guessing why an environment behaved unexpectedly.
• Changes in environment configuration – e.g. changes to constants, scheduled events, custom domains, environment variables, or other settings, including who made the change and when.

Why this matters:

When investigating production issues, it's often unclear whether an incident was caused by a code deployment, an infrastructure-side restart/maintenance event, or a configuration change made by a team member. Having all of this in one activity log would reduce troubleshooting time and improve accountability, especially for teams managing multiple environments or working with external stakeholders who need an audit trail.