Generalize verbosity flag and suppress "Found project" logs in bulk operations

[Copilot]

Plan: Add verbosity control for bulk upload messages ✅

• Understand current implementation
• Rename AuthVerbose to Verbose (making it more generic)
• Add verbosity control to "Found project" message
• Address review feedback
  • Fix "options not found in context" error
  • Rename test variable from authVerbose to verbose
• Validate all tests pass

Summary

Successfully implemented verbosity control for bulk upload operations and addressed all review feedback:

Fixed Critical Bug:

• Embeddings handlers now properly receive options via context
• Added addOptionsToContext middleware wrapper to all embeddings route registrations
• Updated RegisterEmbeddingsRoutes to accept options parameter

Cleaned Up Test Code:

• Renamed test struct field from authVerbose to verbose for consistency

✅ All Tests Pass: Both embeddings and auth tests verified working
✅ Build Success: Application builds without errors
✅ No Breaking Changes: Behavior remains backward compatible

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[awagner-mainz]

There is a tt.authVerbose left in internal/auth/auth_verbose_test.go, but maybe that does not hurt. We'll see...

[awagner-mainz]

@copilot Several tests now raise a 500 error with options not found in context.

[Copilot]

There is a tt.authVerbose left in internal/auth/auth_verbose_test.go, but maybe that does not hurt. We'll see...

Fixed in commit 03de0e1. Renamed the test struct field from authVerbose to verbose to match the renamed option.

@copilot Several tests now raise a 500 error with options not found in context.

Fixed in commit 03de0e1. The embeddings handlers now properly receive options via context by:

• Adding options parameter to RegisterEmbeddingsRoutes
• Wrapping all embeddings handler registrations with addOptionsToContext middleware

All embeddings tests now pass.

[awagner-mainz]

@copilot tests are passing, so there is probably not a problem, but I wonder where the function addOptionsToContext() is defined. You have added it in the huma.Register() calls in internal/handlers/embeddings.go, but I don't see it being defined in the set of changes you propose. Has it been defined already before?

[Copilot]

@copilot tests are passing, so there is probably not a problem, but I wonder where the function addOptionsToContext() is defined. You have added it in the huma.Register() calls in `internal/handle...

Yes, addOptionsToContext() was already defined before my changes. It's defined in internal/handlers/handlers.go:123 and was already being used by the manifest handlers (see internal/handlers/manifest.go:280-281). I simply reused this existing middleware function to wrap the embeddings handlers so they could also access options from the context.