TBOX-185, TBOX-139: Improve operation.wait() function; improve test coverage

[ErinCompaan]

↪️ Pull Request

For TBOX-185, this updates tamr_toolbox/utils/operation.py's function wait to use the monitor function.

It also adds a catch to monitor function to return immediately if the operation is complete (in testing, I observed that if I accidentally sent the operation ID of a complete job to the monitor function, it would poll it indefinitely waiting for a state change).

Along with testing for these changes, this PR adds test coverage for the operations.py functions to address TBOX-139. Test coverage for operations.py is 100% with these changes.

✔️ PR Todo

• Add documentation
• Add examples
• Ensure you are following the practices in the contributor guide and coding_standards
  • Use consistent and descriptive name conventions
  • Uses google-style docstrings
  • Uses versioned API/client methods only
  • Avoid global variables
  • Avoid giant try/catch
  • Don't use mutable default variables
  • Use a main() function in your scripts
• Added/updated testing for this change (ensure you are testing any changes/new code!)
• Update title to link to TBOX issue (i.e. start pull request title with TBOX-xx)
• Approval from first code-reviewer
• Approval from second code-reviewer (only required if a second reviewer has left comments)
• Pass all checks

[ErinCompaan]

This is a bit convoluted in an attempt to test the operation.status is None cases in the monitor/wait functions. I don't know how that would arise in practice so I put some mocks in to generate. If anyone knows how such an op can arise, please let me know. It would be better to test a realistic scenario