Fixes #649: Refresh query_counts.json baseline for current NetBox main

[bctiemann]

Summary

• The tests (main) CI leg was failing on 4 list_objects_with_permission query-count assertions, expecting 2 more queries than NetBox's current main branch actually issues for those views. Confirmed this is pre-existing drift, not caused by any specific PR: it reproduces identically on an unmodified netbox-custom-objects main (see run 31199832224) — an upstream query-count optimization on netbox-community/netbox main shaved 2 queries off these checks since the baselines were last recorded.
• Regenerated netbox_custom_objects/tests/query_counts.json via UPDATE_QUERY_COUNTS=1, run against a clean worktree of NetBox's actual main tip (not a locally cached/stale checkout) to match what CI fetches.
• All four affected keys (customobject-simple, customobject-objectfields, customobject-complex, customobjecttype) dropped by exactly 2 queries each — matching the CI failure precisely. No other baseline keys changed.

Test plan

• python netbox/manage.py test netbox_custom_objects.tests.test_views passes against current NetBox main with the refreshed baseline.
• Re-ran the full plugin suite (1126 tests) against the same environment — no other regressions.
• ruff check clean.

Closes: #649

🤖 Generated with Claude Code

[bctiemann]

Heads up on CI: tests (main) and tests (main, branching) now pass (the original problem), but tests (feature) currently fails with the mirror-image mismatch (expects the new lower counts, but NetBox's feature ref still produces the old higher ones).

Root cause: NetBox core commit b1ee8297d ("Closes #22877: Improve caching logic when retrieving custom fields via get_for_model()") landed on main on 2026-08-06 and shaved ~2 queries off a wide range of core query-count baselines — this plugin's 4 affected views included. It hasn't been merged into feature yet (git log origin/main --not origin/feature still lists it), so main and feature are genuinely, temporarily producing different query counts for the same views right now.

This isn't fixable from this repo — it resolves itself once NetBox core's feature branch is next synced from main. Flagging here so it doesn't block review; not adding a tolerance/skip for it per discussion.