Feature request: fuller Confluence support, including writes

[GuidoLGM]

The Confluence commands in acli are a great start, but they're mostly read-only today. We'd like to see the Confluence surface filled out, with write support in particular.

Why the CLI rather than the REST API: acli authenticates over OAuth, so it works without provisioning a credential. Confluence REST v2 needs an Atlassian API token, and some organisations restrict token creation — ours does. For users in that situation the CLI isn't a convenience, it's the only way to reach Confluence from a terminal. That makes the gaps in acli much more limiting than they'd otherwise be.

As an example — pages. Our use case is publishing generated documentation from a repo into Confluence and keeping it current, which needs roughly:

• create a page, with a parent so it lands in a tree rather than flat
• update an existing page
• read back a page's current version, so a concurrent human edit can be detected rather than silently overwritten

The same pattern applies to other Confluence content — pages are just where it bites us first.

Happy to test against a real instance if that's useful.

Environment: acli 1.3.22-stable, macOS arm64 via the atlassian/acli tap, Confluence Cloud with OAuth.