…FP-737

…ojects (subtask of FP-737) (#467)

* Remove unneeded change

* Fix url for user delete

* Remove logging statements and correct ApiException

Second argument of ApiException is status (i.e. status_code)

* Remove status code in ApiException as TAS returns 200

Main reason for not using TAS return code is that for errors (like
missing user), TAS still returns a 200.  Also, it isn't useful as
we handle all ApiException as 400 and don't log that status_code that
that was pass to ApiException

* Add tests

* Fix pep errors

* Remove change to response for testing purposes

* Fix use of ApiException

* Fix tests

* Improve logging message for forced allocation retrieval

* Fix logging for add/delete of users to allocation

* use projects search; add common component

* revert local dev change

* Complete saga/redux for removing user

Spinner is shown while deleting and error is shown when failed

* Hide remove button for PI user

* Add unit tests

Refactor some fixture into a fixture file

* Add remove user failure saga test

* Refactor removing of user from team from reducer to saga

* Update client/src/redux/sagas/allocations.sagas.js

Co-authored-by: Sal Tijerina <r.sal.tijerina@gmail.com>

Co-authored-by: rstijerina <r.sal.tijerina@gmail.com>

* unified search

* update placeholder

* remove autocomplete package

…o-ui

* Add user functionality and styling

* Text and variable name changes

Co-authored-by: rstijerina <r.sal.tijerina@gmail.com>

* Fix failing tests

* Basic unit test for Allocations Management Modal