feat: Remove document notes from the datatracker

[larseggert]

Fixes #6013

[codecov]

Codecov Report

Merging #6387 (14afcfd) into main (c5a955d) will decrease coverage by 0.11%.
Report is 26 commits behind head on main.
The diff coverage is n/a.

❗ Current head 14afcfd differs from pull request most recent head 93be190. Consider uploading reports for the commit 93be190 to get more accurate results

@@            Coverage Diff             @@
##             main    #6387      +/-   ##
==========================================
- Coverage   88.81%   88.70%   -0.11%     
==========================================
  Files         290      290              
  Lines       40879    40388     -491     
==========================================
- Hits        36305    35826     -479     
+ Misses       4574     4562      -12     

Files	Coverage Δ
ietf/doc/urls.py	100.00% <ø> (ø)
ietf/doc/views_draft.py	92.21% <ø> (+0.27%)	⬆️
ietf/iesg/views.py	93.93% <ø> (+0.26%)	⬆️
ietf/nomcom/urls.py	100.00% <ø> (ø)
ietf/nomcom/utils.py	91.42% <ø> (-2.01%)	⬇️
ietf/nomcom/views.py	93.00% <ø> (-1.62%)	⬇️

... and 3 files with indirect coverage changes

[rjsparks]

Do we really want to remove the note from the database? (I've been on the fence about this). We have the option of removing the ability to edit/make new ones, but show old ones when they existed.

If we want do want to remove it from the database, do we want to move the existing notes somewhere (a dump kept in long-term offline storage, or shifting them to be comments on the document (using DocEvent)? Or is it ok just to throw the information away?

[larseggert]

No, let's keep them in the db. What do I need to change?

[rjsparks]

don't remove the column from the models and remove the migration that came from that change. Then look at the places where you removed how its shown - the emails and all can stay as you've changed them I think, but the html views should show them still if the note is non-empty.

The editing views should all stay removed as the PR currently removes them - if any need to change in the future, the secretariat can[^1] change them using the admin.

---

^1 : We have a separate issue that the secretariat's access to the admin is spotty and needs tuning.