user-specified changes to transient, host, and aperture properties

[djones1040]

Fixes feature request #428. Adds a new option to the /add/ url where people can specify transient coords or redshifts, host coords or redshifts, and global aperture params. New database migration to support user comments and record which fields have been (most recently) updated by a user. Should probably also record which user did the changes but that's not implemented yet. Once updates have been added, task statuses are reset appropriately and the processing queue is re-triggered.

view of the /add/ page

view of the new form

Did all the testing I could think of and everything seems to work, though likely one or two bugs still lurking somewhere. Comments/suggestions welcome.

[manning-ncsa]

@djones1040 Please update the changelog like I did in this PR so that it is easy to merge the changelog entries when we publish a new release.

[manning-ncsa]

@djones1040 We should also have a corresponding unit test for this new feature. Take a look at this one I already made for the form that adds transients by definition. You could create a similar class method like test_update_transient_form() for the purpose.

[djones1040]

@djones1040 Please update the changelog like I did in this PR so that it is easy to merge the changelog entries when we publish a new release.

fixed

[djones1040]

@djones1040 We should also have a corresponding unit test for this new feature. Take a look at this one I already made for the form that adds transients by definition. You could create a similar class method like test_update_transient_form() for the purpose.

done, as ModifyTransientTest in test_views.py

[manning-ncsa]

I'm seeing database transaction errors when I run the test, but they do not cause the new test to fail. In my experience after switching to PostgreSQL this indicates an actual logic error on our part, but since these are unit tests and it is not causing a failure I think we can ignore it until it causes a real problem.

database-1      | 2026-06-28 08:20:44.124 UTC [77] ERROR:  insert or update on table "host_cutout" violates foreign key constraint "host_cutout_transient_id_7c561645_fk_host_transient_id"
database-1      | 2026-06-28 08:20:44.124 UTC [77] DETAIL:  Key (transient_id)=(1) is not present in table "host_transient".
database-1      | 2026-06-28 08:20:44.124 UTC [77] STATEMENT:  COMMIT
app-1           | <Filter: PanSTARRS_g> generated an exception: insert or update on table "host_cutout" violates foreign key constraint "host_cutout_transient_id_7c561645_fk_host_transient_id"
app-1           | DETAIL:  Key (transient_id)=(1) is not present in table "host_transient".