Introduce BraveRpcService

[jrhee17]

Motivation:

The motivation for this PR is better described in #6084

The changeset in this PR attempts to:

• Expose ArmeriaHttpServerParser and ArmeriaRpcServerParser
  • By doing so, users can choose what information must be extracted from BraveService or BraveRpcService. This can provide more flexibility on whether to use only BraveService, only BraveRpcService, or both BraveService and BraveRpcService
• Introduce BraveRpcService which allows users to perform sampling or request/response parsing based on RpcRequest

Modifications:

• Added BraveRpcService. By default, armeria-specific tags/annotations recorded by BraveRpcService is the same as BraveService
• Exposed ArmeriaHttpServerParser and ArmeriaRpcServerParser to allow users to easily construct a RpcTracing or HttpTracing

Result:

• Users may use RpcRequest, RpcResponse to apply sampling/tags/annotations

[github-actions]

🔍 Build Scan® (commit: 45470ae)

Job name	Status	Build Scan®
build-ubicloud-standard-16-jdk-8	✅	https://ge.armeria.dev/s/slsr55il5dada
build-ubicloud-standard-16-jdk-21-snapshot-blockhound	✅	https://ge.armeria.dev/s/tdxwmpuarduk4
build-ubicloud-standard-16-jdk-17-min-java-17-coverage	✅	https://ge.armeria.dev/s/hecgthnfda3y4
build-ubicloud-standard-16-jdk-17-min-java-11	✅	https://ge.armeria.dev/s/37rsk6pshh37o
build-ubicloud-standard-16-jdk-17-leak	✅	https://ge.armeria.dev/s/5nertj7wvrkbk
build-ubicloud-standard-16-jdk-11	✅	https://ge.armeria.dev/s/tzn6r5tpz4k72
build-macos-latest-jdk-21	✅	https://ge.armeria.dev/s/uaclbyhedoe5k

[ikhoon]

Question) Is it possible to share the common logic with BraveService by adding AbstractBraveService and extending it, as you did in AbstractMetricCollectingClient?