feat: add Bifrost LLM gateway service

[mvanhorn]

Summary

Adds Bifrost (the LLM gateway) as a Harbor service, so harbor up bifrost runs it alongside the rest of the stack, modeled on the existing satellite services.

Why this matters

The issue asks for Bifrost as a first-class Harbor service (#224). This follows Harbor's service convention: a services/compose.bifrost.yml, a services/bifrost/ config dir, a default.env block for the port and provider settings, and a serviceMetadata.ts entry so the CLI and UI list it. It mirrors the existing litellm satellite so behavior is consistent with the rest of the stack.

Changes

• services/compose.bifrost.yml plus services/bifrost/.gitignore for the service.
• profiles/default.env entries for the Bifrost port and provider config.
• app/src/serviceMetadata.ts registration so harbor lists and manages it.
• docs/2.3.92-Satellite-Bifrost.md documenting usage.

Testing

• harbor up bifrost brings the service up on its configured port; the service is self-contained (no cross-service healthcheck dependency).

Closes #224

[av]

Hi, thank you so much for the contribution!

We already have bifrost as a service in Harbor, please see the docs here:
https://github.com/av/harbor/wiki/2.3.84-Satellite-Bifrost

Please let me know if you need something specific from this integration that isn't otherwise present :)

[mvanhorn]

Ah, my miss - I hadn't found the existing bifrost satellite before opening this. The built-in integration covers what I was after, so closing this one. Thanks for the pointer!