Create a workflow for testing dev environments

[mr-cal]

Overview

Our development environment should be tested across a variety of distros and architectures.

Rationale

Project maintainers rarely set up pristine development environments, so we rarely experience what it's like for new contributors to follow our getting started guides.

Specification

• Create a test-dev-environment.yaml workflow that runs:

make setup
make lint
make format
make test
make docs

• Run the workflow in clean LXD environments.
  • Note that a github runner isn't a good environment, since it has tons of pre-installed software.
• By default, the workflow should run 6 tests with the matrix:
  • distros
    • Ubuntu 22.04
    • Ubuntu 24.04
    • Debian Trixie
  • architectures:
    • amd64
    • arm64
• The distros and architectures should be configurable inputs, similar to other workflows (example)
• Create a self-test-dev-environment.yaml workflow that clones starbase and runs the test-dev-environment.yaml workflow
• Use this workflow in starbase (Use starflow's dev environment workflow starbase#438)

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-4739.

This message was autogenerated

[PraaneshSelvaraj]

While working on craft-providers, I ran into an edge case related to ty versioning during make setup.

If ty is already installed locally (e.g. an older version), make setup reuses it since it only checks for presence, not version. This led to different lint behavior compared to clean Ubuntu setups where the snap version auto-updates.