LF-4309 Complete form breaks when not completed fast enough allowing page to time out or something

[kathyavini]

Description

This PR removes the passing of the purpose and method keys from the saga to the task utility functions in favour of using { shouldUnregister: true } on the inputs that need to be nulled when their method_id / purpose_id is not selected

Notes:

• Removing the calls to api.endpoints.getSoilAmendmentPurposes.select()(state), fixes the timeout that makes the form unsubmittable after the api cache expires
• <Unit /> component needed a little bit of adjustment to accept shouldUnregister: true
• A cleanup before insert on the model was still needed on PATCH, but I feel this is an appropriate place for it because
  • Nothing is wrong with the PATCH request, it is correctly only giving the updated data, which means it doesn't overwrite any old data in the other fields (e.g. other_application_method), potentially triggering the check constraint
  • There is no longer any ambiguity about what data is correct
  • It is logical + readable on the model where it is defined specifically on PATCH (update)
• the code changes (not sure if it's merely shouldUnregister or the task flow revert as well) resolves the other persistence bugs we saw; I will re-test this momentarily then indicate their tickets below as well
  • Update: needed to fix some logic and now those are resolved as well

Jira link: https://lite-farm.atlassian.net/browse/LF-4309

• https://lite-farm.atlassian.net/browse/LF-4324 (non-update of furrow depth)
• https://lite-farm.atlassian.net/browse/LF-4329 (non-update of other application method)
• https://lite-farm.atlassian.net/browse/LF-4333 (non-update of application method itself)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Passes test case
• UI components visually reviewed on desktop view
• UI components visually reviewed on mobile view
• Other (please explain)

Checked on the soil_amendment_task product table and the soil_amendment_task_products_purpose_relationship table of db.

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The precommit and linting ran successfully
• I have added or updated language tags for text that's part of the UI
• I have added "MISSING" for all new language tags to languages I don't speak
• I have added the GNU General Public License to all new files

[SayakaOno]

Also confirmed that https://lite-farm.atlassian.net/browse/LF-4333, https://lite-farm.atlassian.net/browse/LF-4329 and https://lite-farm.atlassian.net/browse/LF-4324 were fixed.
Thank you!

[Duncan-Brain]

I don't know if I would have undid the updated naming since soil_amendment_task has meaning and does not have property of soil_amendment_task_products.

[Duncan-Brain]

Always love a net removal of code! ❤️

I like what you are saying for PATCH being able to make the decision that a POST could not 👍 . I think we will need to add to this for weight and volume too. I thought I saw a similar bug there.