Update Poetry Version

[BryonLewis]

• Older version of poetry we were using (1.1.2) was causing some build errors.
• Updated to the latest version (1.2.0) but it had different behaviors when determining that the currently used python virutalenv was active.
• From the Poetry Environment Management Docs it should recognize that it is inside of a venv and not create a new one. It did this properly for the 1.1.2 version but not for 1.2.0.
• To force it to recognize the the virtualenv I had to set the Environment variable manually.
• Additionally, on the worker container, I needed to make sure it did a full copy of the files and didn't use symbolic links for the venv. The final container for the worker is based off a VIAME GPU algorithms container so it isn't guaranteed to have the same symlink python pointers. This works for the girder/web container because the builder and the final container both use the same base python3.8.
• Also modified the pyproject.toml to support a more updated structure.

[waxlamp]

Thanks for this fix, @BryonLewis. Has the Poetry bug been reported upstream? If not, can you do so?

[BryonLewis]

I haven't spent significant time searching within the Poetry Github to see if it was a regression, intended change from jumping from 1.1.2 past 1.1.15 and all the way to 1.2.0 or if there is duplicate issue already (poetry has 991 backlogged issues). I imagine we were taking advantage of some quirk which allowed it to identify virtualenvs indirectly. Explicitly stating them allowed us to update to the latest version. I ran the integration tests and they all worked (except one related to updating the addons).

[marySalvi]

LGTM