Pin the NetBox Docker version in the docker-compose.yml file

[cimnine]

Related Issue: n/a

New Behavior

The version of the NetBox Docker image in the docker-compose.yml file is pinned to the specific minor version compatible with the current release of NetBox Docker.

Contrast to Current Behavior

Currently we use the latest tag by default.

But the NetBox Docker images are tagged with the version of NetBox they contain.
But only certain releases of NetBox Docker support certain versions of NetBox.
This lead to frustration when upgrading for a lot of users, because it's not obvious how the versions (NetBox Docker, NetBox, NetBox Docker image) are tied to each other.

The latest tag might point to a version of NetBox, which is not yet supported by NetBox Docker. This leads to frustration.

Discussion: Benefits and Drawbacks

By pinning the specific version of NetBox we support, I hope to reduce that frustration. I.e. that a user runs docker compose pull in the project's directory, which will eventually fetch a version of the NetBox Docker image that is not yet supported.

Changes to the Wiki

There should be no changes necessary.

Proposed Release Note Entry

## The NetBox Docker image is pinned to the supported NetBox minor version in `docker-compose.yml`

Previously, the `docker-compose.yml` always pointed towards the `latest` tag of the NetBox Docker image.
This has lead to frustration, if `latest` pointed to a version of NetBox that was not yet supported by the NetBox Docker project.

By pinning the version of NetBox in the `docker-compose.yml`, we increase the chance that a given version of NetBox Docker fetches a NetBox Docker image that is compatible.

Double Check

• I have read the comments and followed the PR template.
• I have explained my PR according to the information in the comments.
• My PR targets the develop branch.