feat: archive vehicles

[choffmann]

Close #430

[xk0niR]

• Create a new vehicle: OK
  

• Create new watering plan: OK
  

• Delete vehicle: OK

• Open watering plan: ERROR

I am unable to open the watering plan. Backend shows
"error="entity not found: WateringPlan"

Also I created another vehicle and since then I am unable to open watering plan page
"DEBUG internal/storage/postgres/watering_plan/get.go:92 failed to get linked vehicle entity by id and vehicle type user_id="9fddda2f-657d-4b81-b852-8a333ea2b4a1" error="no rows in result set" watering_plan_id="9" vehicle_type="trailer""

Edit: Last message may not related to another vehicle being created. It could be watering plan overview was loading fine because broken watering plan was on 2nd page. If another watering plan gets deleted and the broken watering plan moves to 1st page you can´t load the site anymore.

[xk0niR]

@choffmann Since we alter database table doesn´t the seed also to be updated?

[choffmann]

@xk0niR I haven't touched the frontend yet. The delete endpoint is still active and will delete the entity from the database. To test it, you need to manually archive the vehicle via the backend api route POST /api/v1/vehicle/archive/:id

[choffmann]

@choffmann Since we alter database table doesn´t the seed also to be updated?

@xk0niR No, I have implemented an archive_at attribute in the db which is set to null by default

[xk0niR]

Tested using swagger with vehicle id 3
Archive:

List all archived vehicles:

Vehicle is also no longer inside get-all-vehicles and get-vehicle-by-id also works.
Works 🥇