Feature/migrate to poetry

[michael-bentz]

What does this change do?

This change migrates the project to use poetry for dependency management.

Why was this change made?

To align dependency management with other projects.

Verification

1. Verify that all automated tests pass
2. Update the report_handler dependency in PyCustodian

• 

3. Update dependencies with poetry install
4. Run the sample script and verify that a xlsx report is generated that contains entries.

Affirmations

All of these should have a check by them. Any exception requires an explanation.

• I have added docstrings with details on keyword arguments to new functions following the convention detailed in this gist
• I have added type hinting to new function parameters.
• I have added tests to new functions, following the rules of F.I.R.S.T..
• I matched the style of the existing code.
• I added and updated any relevant documentation (inline, README, CHANGELOG, and such).
• I used Python's type hinting.
• I ran the automated tests and ensured they ALL passed.
• I ran the linter and ensured my changes have not introduced ANY warnings or errors.
• I have made an effort to minimize code changes and have not included any cruft (preference files, *.pyc files, old comments, print-debugging, unused variables).
• I have made an effort maintain a clear commit history (haven't merged other branches or rebased improperly).
• I have written the code myself or have given credit where credit is due.

[sinarest1608]

@mbentz-uf
All tests passed and a report was generated but not in the reports directory but in the root. Not sure if that is supposed to be.

[michael-bentz]

@sinarest1608 Yes, if you debug the sample script you can see that this line creates the file at the current working directory:

https://github.com/ctsit/PyCustodian/blob/bbb6b89949e13e8bd452091ece154c2cb31ba153/py_custodian/scripts/sample_script.py#L21

[sinarest1608]

Looks good to me.