Starlette instrumentation's `instruments` version is too restrictive

[aabmass]

The starlette instrumentation specifies

opentelemetry-python-contrib/instrumentation/opentelemetry-instrumentation-starlette/pyproject.toml

Lines 36 to 39 in b76119b

	[project.optional-dependencies]
	instruments = [
	"starlette ~= 0.13.0",
	]

opentelemetry-python-contrib/instrumentation/opentelemetry-instrumentation-starlette/src/opentelemetry/instrumentation/starlette/package.py

Line 16 in b76119b

_instruments = ("starlette ~= 0.13.0",)

This does not mean >=0.13, it actually means starlette>=0.13.0,<0.14.dev0. Concretely this overly narrow requirement is causing resolution issues with the new UV workspace introduced in #3124 and the google-genai instrumentation PR #3256.

...
      And because opentelemetry-instrumentation-starlette[instruments] depends on starlette>=0.13.0,<0.14.dev0 and opentelemetry-instrumentation-fastapi[instruments] depends on fastapi>=0.58, we can conclude that all of:
...

[aabmass]

@Kludex @emdneto this is making tox -e ruff precommit fail, because of d092c1a

[emdneto]

@Kludex @emdneto this is making tox -e ruff precommit fail, because of d092c1a

Now the tox -e ruff doesn't make sense; we can probably change the name to pre-commit instead

[aabmass]

Now the tox -e ruff doesn't make sense; we can probably change the name to pre-commit instead

I agree, but I think it might be a little annoying to people with muscle memory for tox -e ruff. Is it possible to keep tox -e ruff for just running ruff somehow?

[emdneto]

@aabmass I think this, or create separated jobs for ruff, ruff-format and uv-lock.

diff --git a/tox.ini b/tox.ini
index c55482e7..f64bce06 100644
--- a/tox.ini
+++ b/tox.ini
@@ -1006,6 +1006,18 @@ commands =
 
 [testenv:ruff]
 basepython: python3
+setenv =
+  SKIP=uv-lock
+deps =
+  -c {toxinidir}/dev-requirements.txt
+  pre-commit
+commands =
+  pre-commit run --color=always --all-files {posargs}

We can keep ruff in tox only and exclude it in workflows