test/dev-cmd/developer_spec: add usage test

[scpeters]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them? Performance claims (e.g. "this is faster") must include Hyperfine benchmarks.
• Have you written new tests (excluding integration tests) for your changes? Here's an example.
• Have you successfully run brew lgtm (style, typechecking and tests) with your changes locally?

---

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes. Non-maintainers may only have one AI-assisted/generated PR open at a time.

---

After adding a test for brew unbottled in #22050, I noticed that it would be straightforward to also add a test for brew developer, expecting that brew developer succeeds and prints
"Developer mode is disabled" by default.

[MikeMcQuaid]

Thanks again @scpeters!