Giza integration tests: Joystream CLI: Channel and video categories flow

Parameters:

• Tv - total number of video categories to create
• Tc - total number of channel categories to create
• Uv - total number of video categories to update
• Uc - total number of channel categories to update
• Fv - final number of video categories
• Fc - final number of channel categories

Constraints:
0 < Fc <= Tc - 2 (at least 2 channel category deletions need to be executed - one by lead and one by curator)
0 < Fv <= Tv - 2 (at least 2 video category deletions need to be executed - one by lead and one by curator)
2 <= Uc <= Tc
2 <= Uv <= Tv

Preconditions:

• A running Joystream node
• A running query node
• Curator lead is hired
• Optionally: There is a curator group with at least 1 curator (it can also be created in this flow)

Post-execution state:

• There are Fv new video categories and Fc new channel categories

Optimistic flow:

• Create Tv video categories (use curator/lead context interchangeably)
• Create Tc channel categories (use curator/lead context interchangeably)
• Update Uv video categories (use curator/lead context interchangeably)
• Update Uc channel categories (use curator/lead context interchangeably)
• Remove Tv - Fv video categories (use curator/lead context interchangeably)
• Remove Tc - Fc channel categories (use curator/lead context interchangeably)
• Verify final state (F) against query node

Possible additional failure cases to include:

• Create/Update/Remove channel/video category using curator context&key while not beeing part of curator group: expect exit code 405 - AccessDenied
• Create/Update/Remove channel/video category using non-curator key: expect exit code 405 - AccessDenied
• Create/Update category with invalid metadata as input: expect exit code 400 - InvalidInput
• Update/Remove non-existing channel/video category: expect exit code 400 - InvalidInput

No files or test entry points are named in the issue. Start by locating the Joystream CLI integration-test entry point and the existing channel/video category flows, then exercise creation, updates, removals, authorization failures, invalid metadata, and missing categories. Done means the final counts match the query node and the listed failure cases produce the expected exit codes.