Change Release, Prerelease Workflow Container Images

[bryanculver]

Proposed Changes

Change the containers we build and publish in next and develop.

• nautobot-dev (layer final-dev): Publish min and max supported Python versions
  • 3.7,3.11 for develop
  • 3.8,3.11 for next
• nautobot (layer final): Build and Publish only max supported Python version
  • This would drop publishing earlier Python version images (even if still supported)
  • Keep 1.5.X as-is: Publish the same matrix of Python versions
  • 1.6.0+: Publish only the max version (3.11 as of writing this)
• Change POETRY_PARALLEL to be True in the release workflows

Plugins will still be able to use "branch version" images for CI testing and developing locally.

Justification

• Speed up CI integration runtimes (frequently times out, uses many runners)
• Improve our Actions cache utilization (fit more within cache with fewer evictions and speed up rebuilds)
• Many cases of deployers rolling their own Docker image anyway
• Publishing max vs publishing min Python version for nautobot image: Many apps have a higher lower bound due to their direct dependencies but Nautobot is slower to adopt a newer upper bound for stability reasons.

[glennmatthews]

This should include enabling Python 3.11 in both develop-1.6 and next, IMHO.

[glennmatthews]

Actually it looks like updating to support 3.11 requires some dependency updates; I'll handle that in a separate PR.

[glennmatthews]

#4118 for develop-1.6.

[snaselj]

Fix if conditions not to be string:

.github/workflows/prerelease.yml
153: if: "${{ env.SLACK_WEBHOOK_URL != '' }}"

.github/workflows/release.yml
159: if: "${{ env.SLACK_WEBHOOK_URL != '' }}"