ci: Skip package build on tox runs

[TheRealFalcon]

Proposed Commit Message

ci: Skip package build on tox runs

Building a wheel/sdist generally adds 5+ seconds to every tox run.
This is unnecessary because a built package isn't needed to run any
of the CI tasks.

Also remove the `recreate` line as it wasn't doing anything. To work
correctly, it should be defined under `[testenv]`,
not `[tox]`.

Additional Context

tox -e ruff is near instant on Python 3.8+

recreate lives under https://tox.wiki/en/latest/config.html#tox-environment

Test Steps

Checklist

• My code follows the process laid out in the documentation
• I have updated or added any unit tests accordingly
• I have updated or added any documentation accordingly

Merge type

• Squash merge using "Proposed Commit Message"
• Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)

[holmanb]

I like this idea. We won't exercise package build as much as a result, but I don't see that as a loss. We do that in the CI integration job, and plenty in our integration tests too.

Maybe give other other devs a chance to object before merging?

[aciba90]

LGTM, thanks!

[blackboxsw]

LGTM. Let's try this out to ease the time costs of CI and local tox runs to cut down on the recurring cost of development and testing. While I like that our CI tests happen to exercise the package build, We can easily run any of the following on PRs that happen to be packaging related

• make deb
• ./packages/bbdeb -S
• or tox --override testenv.package=wheel or something to validate no degradation in behavior on those branches