text: Title: Refactor `alert_view.py`
  Body: ## Tell us about the problem you're trying to solve
  
  In the [`alert_view.py`](https://github.com/chaos-genius/chaos_genius/blob/04cfe2ee0e82ff627fa29f8f50ccc08b6ba52bef/chaos_genius/views/alert_view.py) file, database calls and other functionality are directly included in the route functions.
  
  ## Describe the solution you'd like
  
  Ideally, these should be present as functions in the [alerts controller](https://github.com/chaos-genius/chaos_genius/blob/main/chaos_genius/controllers/alert_controller.py) which are simply called in the route functions.
  
  For example, this: https://github.com/chaos-genius/chaos_genius/blob/04cfe2ee0e82ff627fa29f8f50ccc08b6ba52bef/chaos_genius/views/alert_view.py#L140-L148
  
  should be separated in a `def enable_alert(alert_id: int)` function.
  
  A good rule of thumb to check if it's abstracted enough is that the view file should not import the DB model directly (in this case, it is the `Alert` model).
  
  ## Describe alternatives you've considered
  
  N/A
  
  ## Additional context
  
  N/A
  
  ---
  
  Please leave a reply or reach out to us on our [community slack](https://github.com/chaos-genius/chaos_genius#octocat-community) if you need any help.