test checklist for ooni/backend components in development environment

[aagbsn]

#300 adds these paths to the load balancer configuration:

• /api/v1/geolookup
• /api/v1/collectors
• /bouncer/net-tests
• /api/_/debug_prioritization
• /api/v1/test-list/tor-targets
• /api/_/show_countries_prioritization
• fix generated apidocs for endpoint /bouncer/net-tests

We need a checklist of tests to make sure that the oonprobe client works correctly on the development environment before deploying to production.

[aagbsn]

I think we just agree that the bouncer/net-tests swagger API generated test isn't that important. Basically if you define the route handler with named fields it will still raise a ValidationError; the only way to catch the exception and return a different status code for a single route is to parse the request body inside the handler definition with a try/except and then raise the HTTPException you want and that means there isn't a pydantic model to generate the API test, eh. I added a docstring to the method so it is at least documented in this PR ooni/backend#1055