Support more flexible hostnames

[evaline-ju]

Description

As an orchestrator user, I want to configure orchestrator with various models, so that I can try guardrailing a variety of models.

Discussion

Currently the orchestrator validation will allow for hostnames that have one part i.e. hostname.company.com. However, multiple models could be served as part of that, e.g. hostname.company.com/model-name, which would cause an error like Error: invalid hostname: chat_generation has an invalid hostname.

Acceptance Criteria

• Unit tests cover new/changed code
• Examples build against new/changed code
• READMEs are updated
• Type of semantic version change is identified

[declark1]

Hmm, it technically isn't a hostname at that point, so perhaps we need to support adding a path prefix? Won't requests be flowing through a router though? The config isn't designed to specify servers for multiple models.