feat: Do not set ProposedPerson = NULL when ResetWorkflow

[aleklundeq]

• New feature
• Bug fix
• High impact

Description of work:
When resetting workflow as a step in rejecting a AllocationRequest I have removed functionality to set ProposedPerson to NULL. This is an attempt to make ProposedPerson available when the task owner is responding to a rejected request, which should be to create a new request. It is then easier to know who was the previous suggested resource before creating a new request

Testing:

• Can be tested
• Automatic tests created / updated
• Local tests are passing

Can be tested by creating a new request with a specific resource (as proposedPerson). Then the resource owner should reject the request. The rejected request should then still contain the proposedPerson suggested in the first step.

Checklist:

• Considered automated tests
• Considered updating specification / documentation
• Considered work items
• Considered security
• Performed developer testing
• Checklist finalized / ready for review