Create Limits for the confidential-http capability

[prashantkumar1982]

The limits just mirror what's there for http-actions capability.

[github-actions]

✅ API Diff Results - No breaking changes

---

📄 View full apidiff report

[Copilot]

Pull request overview

This PR adds per-workflow limit settings for the ConfidentialHTTP capability, mirroring the existing HTTPAction limits so that confidential HTTP calls are governed by the same configuration framework.

Changes:

• Extend the Workflows schema with a new ConfidentialHTTP section and corresponding confidentialHttp struct, defining call limit, connection timeout, and request/response size limits.
• Update default configuration sources (defaults.toml, defaults.json) to include PerWorkflow.ConfidentialHTTP defaults aligned with HTTPAction.
• Update tests and the README’s limits diagram to cover and document the new ConfidentialHTTP settings.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
pkg/settings/cresettings/settings.go	Adds ConfidentialHTTP to the Workflows schema and defines the confidentialHttp struct and its default values, paralleling HTTPAction.
pkg/settings/cresettings/settings_test.go	Extends the schema unmarshal test to include ConfidentialHTTP config and asserts its default call and request size limits.
pkg/settings/cresettings/defaults.toml	Adds a [PerWorkflow.ConfidentialHTTP] block with default call, timeout, and size limits.
pkg/settings/cresettings/defaults.json	Adds a PerWorkflow.ConfidentialHTTP object mirroring the TOML defaults.
pkg/settings/cresettings/README.md	Updates the Mermaid limits diagram to include a PerWorkflow.ConfidentialHTTP subgraph and its bounds.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jmank88]

Suggested change

	type confidentialHttp struct {
	type confidentialHTTP struct {