Job update and Resource Booking update should use PATCH instead of PUT

[maxceem]

In the TaaS App we have the ability to:

• Edit Job https://platform.topcoder-dev.com/taas/myteams/16873/positions/ecaf2c7f-2b43-4397-bcf5-0ddf38c7f6a6/edit
• Edit Resource Bookings https://platform.topcoder-dev.com/taas/myteams/16873/rb/f0738f2a-c837-42e3-acdf-0e1324d77e53/edit

Internally, when save update we use PUT request:

• https://github.com/topcoder-platform/taas-app/blob/feature/fix-job-edit-permissions/src/services/jobs.js#L65
• https://github.com/topcoder-platform/taas-app/blob/feature/fix-job-edit-permissions/src/services/resourceBookings.js#L28

This appears to have a drawback. If we add some new field in the TaaS API but we don't update the form then fields that are not supported by the form would be reset to null and cause issue like this topcoder-platform/taas-apis#260

Taks:

• we have to use PATCH requests instead of PUT to make it totally safe, so we never would lost any fields
• we have to make sure that we still can clear data in the form for optional fields and the server would accept it and correctly clear that data

[maxceem]

QA guidelines:

• we have to make sure that we can clear any optional value in the RB edit form and Job edit form
• test create Job

[sandhiyakavi]

@maxceem Verified the following scenarios,

1. Verified creating Job from Connect as well as Taas app, its getting created successfully.
2. Verified Editing Job as well as RB form by clearing all the optional values, it's updating to null.

bandicam.2021-05-28.13-33-53-166.mp4

bandicam.2021-05-28.13-43-12-746.mp4