feat: list event logs with meshstack eventlog list

[JohannesRudolph]

🤖 Written by AI agent

Adds meshstack eventlog list [--title T] [--from D] [--until D], with the usual --limit and -o.

Why: scripts that count what happened in a meshStack need the event log, because an object that was deleted again leaves only its event behind. The first user is the trial adoption script in meshcloud/meshfed-release#10965. It can drop its own login, token renewal and paging, and call --limit unlimited -o ndjson instead.

• The listing asks for createdAt,asc, so a new event lands on the last page and does not shift pages that are still to come.
• --from and --until take a date (midnight UTC) or an RFC 3339 instant.
• --workspace narrows an admin listing to one workspace, as in the other list commands.

Checked against try.meshstack.io with a browser login in the admin workspace: three titles listed in full with --limit unlimited, up to 297 events over 6 pages, with no duplicates and sorted oldest first.

🤖 Generated with Claude Code

[meshcloud-gh-actions]

Coverage of the acceptance run against the meshStack backend, on c04ff5beba1e0444b872adb3d80e9e4975fa12f2.

Scope	Coverage
Unit tests	75.6%
Acceptance tests	8.8%
Combined	75.6%

Uncovered functions

client/api_key.go:55: meshApiKeyClient.Create 0.0%
client/api_key.go:59: meshApiKeyClient.Read 0.0%
client/api_key.go:63: meshApiKeyClient.Update 0.0%
client/api_key.go:71: meshApiKeyClient.Delete 0.0%
client/api_key_permissions.go:20: ApiKeyPermissions.AllCodes 0.0%
client/api_key_permissions.go:33: ApiKeyPermissions.WorkspaceCodes 0.0%
client/api_key_permissions.go:295: AllApiKeyPermissions 0.0%
client/api_key_permissions.go:299: WorkspacePermissionCodes 0.0%
client/building_block_definition.go:71: MeshBuildingBlockDefinitionApprovalPolicies.NothingRequiresApproval 0.0%
client/building_block_definition.go:82: DisabledSchedule 0.0%
client/building_block_definition.go:89: MeshBuildingBlockDefinitionSchedule.IsDisabled 0.0%
client/building_block_definition.go:93: MeshBuildingBlockDefinitionSpec.HasNeutralPolicies 0.0%
client/building_block_definition.go:97: MeshBuildingBlockDefinitionSpec.WithNeutralPolicies 0.0%
client/building_block_definition.go:166: meshBuildingBlockDefinitionClient.List 0.0%
client/building_block_definition.go:173: meshBuildingBlockDefinitionClient.Read 0.0%
client/building_block_definition.go:177: meshBuildingBlockDefinitionClient.Create 0.0%
client/building_block_definition.go:181: meshBuildingBlockDefinitionClient.Update 0.0%
client/building_block_definition.go:185: meshBuildingBlockDefinitionClient.Delete 0.0%
client/building_block_definition_version.go:98: TagInputTargetsFor 0.0%
client/building_block_definition_version.go:233: meshBuildingBlockDefinitionVersionClient.List 0.0%
client/building_block_definition_version.go:239: meshBuildingBlockDefinitionVersionClient.Create 0.0%
client/building_block_definition_version.go:248: meshBuildingBlockDefinitionVersionClient.Update 0.0%
client/building_block_definition_version_implementation.go:107: *MeshBuildingBlockDefinitionImplementation.UnmarshalJSON 0.0%
client/building_block_run.go:75: meshBuildingBlockRunClient.ListRawSeq 0.0%
client/building_block_run.go:79: meshBuildingBlockRunClient.GetLogs 0.0%
... and 141 more

covdata func names a method without its receiver, so an entry can belong to an implementation nothing selects rather than to a function the tests never reached. Open the file and line before reading one as a coverage gap.

[grubmeshi]

Superseded by #23, which brings this work together with #10, #11, #12 and #21, rebased on main and reviewed. I'm closing this PR by deleting its branch.