Use forms in destination page

[hmpf]

Depends on #936

Review file by file

Will be squashed

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 48.02632% with 158 lines in your changes missing coverage. Please review.

Project coverage is 77.45%. Comparing base (a3311e0) to head (b4c8a33).
Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
src/argus/htmx/destination/views.py	18.18%	90 Missing ⚠️
src/argus/notificationprofile/media/base.py	63.10%	38 Missing ⚠️
src/argus/htmx/destination/forms.py	0.00%	15 Missing ⚠️
src/argus/notificationprofile/media/email.py	80.95%	8 Missing ⚠️
src/argus/notificationprofile/media/__init__.py	42.85%	4 Missing ⚠️
src/argus/notificationprofile/serializers.py	89.47%	2 Missing ⚠️
...rc/argus/notificationprofile/media/sms_as_email.py	83.33%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1161      +/-   ##
==========================================
- Coverage   78.48%   77.45%   -1.03%     
==========================================
  Files         141      141              
  Lines        5442     5553     +111     
==========================================
+ Hits         4271     4301      +30     
- Misses       1171     1252      +81     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stveit]

Some issues while testing this:

Trying to update a destination gives the error "This email destination already exists." This happens if you make no changes to the form and click "update", or only change either label or the setting. But if you change both to unique values that are not used in another destination, then it updates. It seems like the validation doesn't understand that the updated destination will replace the original, and just treats it like you're trying to create a new destination with the same label and or setting.

Simultaneously, a new collapse elements is created that is empty with the title (0)

Another problem (relevant comment here is when you try to create a new destination (or update) with a label or email that collides with an existing destination, you get the error message "This email destination already exists", but it does not indicate in any way if the problem is the label, the email or both