[PRODCRE-792] Per-method onchain config for capabilities V2

[bolekk]

1. Add per-method config - each method can be either a trigger or an executable.
2. Include some extra fields that were previously hardcoded in Launcher.

[github-actions]

apidiff results - backwards-incompatible changes detected ❌

Module: github-com-smartcontractkit-chainlink-common

Status: ❌ 6 incompatible, 50 compatible

Incompatible Changes (6)

Element	Change
./pkg/capabilities.RemoteExecutableConfig.RegistrationExpiry	removed
./pkg/capabilities.RemoteExecutableConfig.RegistrationRefresh	removed
./pkg/capabilities/pb.(*RemoteExecutableConfig).GetRegistrationExpiry	removed
./pkg/capabilities/pb.(*RemoteExecutableConfig).GetRegistrationRefresh	removed
./pkg/capabilities/pb.RemoteExecutableConfig.RegistrationExpiry	removed
./pkg/capabilities/pb.RemoteExecutableConfig.RegistrationRefresh	removed

(Full summary: https://github.com/smartcontractkit/chainlink-common/actions/runs/17470297807/#summary-49616699898)

[fernandezlautaro]

I'll add a comment here saying the key has to match the exact literal value of the capability's proto file like LogTrigger (trigger), WriteReport (action/executable), GetTransactionByHash (action/executable) as the generated Go code for the actions will be consistent, but for the trigger will prepend the Register, such as RegisterLogTrigger and the method to be added to that map is LogTrigger and not RegisterLogTrigger)

[bolekk]

I think the prefixes are an implementation detail and the SDK will use methods exposed to the users.