Enable Upstream Testing

[bryanculver]

Closes: #DNE

What's Changed

• Updated Dockerfile to be compatible with upstream testing
• Updated invoke, Dockerfile defaults which are incompatible with pyproject.toml
• Added workflow fragment to trigger testing

TODO

• Explanation of Change(s)
• Added change log fragment(s) (for more information see the documentation)
• Attached Screenshots, Payload Example
• Unit, Integration Tests
• Documentation Updates (when adding/changing features)
• Outline Remaining Work, Constraints from Design

[bryanculver]

next is expected to fail because it goes to a new major version of Nautobot so can be safely ignored for now.

[bryanculver]

Tried to use poetry self update to deal with nautobot-dev containers potentially having an older version of Poetry where CI/dev might have a newer one and mint a lock file that is too new (see: https://github.com/networktocode-llc/cookiecutter-ntc/pull/276#discussion_r974383161, https://github.com/nautobot/nautobot-plugin-chatops/actions/runs/4088225247/jobs/7049757009#step:7:194).

[smk4664]

Thanks Bryan for fixing the CI and improving the process! Hopefully in the future we can just use poetry instead of the pip install with constraints.

[bryanculver]

Thanks Bryan for fixing the CI and improving the process! Hopefully in the future we can just use poetry instead of the pip install with constraints.

Until something like this comes in: python-poetry/poetry#7051 I don't think we can go all-in for Poetry for this use case. We need to test a package within an environment of already installed packages. We don't need to be hand-crafting multiple lock files or pyproject.tomls.