refactor(wolf-rbac): separate route and consumer settings

[shreemaan-abhishek]

Description

wolf-rbac currently mixes Wolf connection/output settings with Consumer identity. This makes Route behavior depend on Consumer configuration that is unavailable before a Consumer is matched.

This PR:

• keeps only required appid in Consumer configuration
• moves server, header_prefix, and ssl_verify to Route/Service configuration
• clears the Route header namespace before authentication and sets it only after Wolf succeeds
• updates public API routes and documentation

This is a breaking schema change.

Migration

Before upgrading, move server, header_prefix, and ssl_verify from each Consumer to every Route/Service using wolf-rbac; leave only appid on the Consumer. If Consumers used different values on one Route, split or standardize those settings. Routes exposing Wolf APIs must configure both public-api and wolf-rbac.

Checklist

• I have explained the need for this PR and the problem it solves
• I have explained the changes or the new features added to this PR
• I have added tests corresponding to this change
• I have updated the documentation to reflect this change
• I have verified that this change is backward compatible (this is an intentional breaking schema cleanup)