feat(actors ls): add --public / --private flags to filter actors by visibility

[kuntal1461]

Problem

apify actors ls and apify actors ls --my return a mixed list of public and private actors with no way to filter by visibility. Users who manage many actors must open the Apify Console to see which ones are public or private — there is no CLI equivalent.

This becomes painful when:

• You want to audit which of your actors are accidentally public or unintentionally private.
• You are scripting actor lifecycle workflows (e.g. "list all private actors and publish the ones that pass CI") — today this is impossible in a shell script without scraping the Console UI.
• Your team enforces that only release-ready actors are public and needs a quick way to verify that from the terminal.

Proposed feature

Add two mutually exclusive flags to apify actors ls:

--public     Show only public actors
--private    Show only private actors

Usage examples

# See all your private actors at a glance
apify actors ls --my --private

# Find public actors and pipe into further automation
apify actors ls --my --public --json | jq '.items[].name'

# Paginate through private actors
apify actors ls --private --limit 10 --offset 20

# Error: flags are mutually exclusive
apify actors ls --public --private

Why this helps users

Scenario	Today	With this feature
Audit: which actors are private?	Open Console, filter manually	apify actors ls --my --private
Script: process only public actors	Impossible without Console scraping	apify actors ls --public --json
Verify a newly published actor is public	Check Console UI	apify actors ls --my --public and scan the list
CI pipeline: assert no test actor went public	No CLI check possible	apify actors ls --my --public --json and check count

The Console already surfaces a Published / Not-published toggle. This feature brings that same visibility filter to the CLI, making the two surfaces consistent and enabling automation that the Console cannot support.

[l2ysho]

@patrikbraborec please check if this idea make sense from product side.

[patrikbraborec]

Hi @l2ysho & @kuntal1461, it seems OK for me. It is not high priority from my POV, though.