Setting Committed By date to the same date as Needed By date doesn't move the dependency to committed automatically

Issue Summary

Setting Committed By date to the same date as Needed By date doesn't move the dependency to committed automatically

Steps to Reproduce

1. Create a new dependency
2. Fill out Title, Description, Program Increment, associate with Feature
3. Select a Program under Requesting > Program
4. Select another Program under Depends On > Programs
5. Set a Needed By date(any date: example 8/31/2022)
6. Save
7. Set a Committed By date to some future date than the above date (eg 9/4/2022)
8. Propose Date shows ‘Yes’ selected by default
9. Save
10. Accept proposal
11. Dependency is Committed. This is all good
12. Now the below steps to see the same date behavior
13. Either create a new dependency with steps 1-4 above; or continue on the same dependency above
14. Now set the Needed By date to some date (any date, eg 9/2/2022)
15. Save
16. Committed By field becomes blank
17. Set Committed By date to the same date as the Needed By date above (9/2/2022)
18. Notice the Propose Date does not pop-up (this makes sense)
19. Save
20. Dependency shows NOT COMMITTED still (This is not expected)
21. Notice the Propose Date displays with ‘No’ selected 
22. Change Propose Date to 'Yes'
23. Save
24. Now Dependency is Committed

Expected Results

Expected behavior on Step 20- Dependency should move to Committed without doing step 22-23. (PM input may be required to validate this)

Actual Results

Dependency is not auto committed when setting same date

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available