Clarify ARCHIVED filtering is caller-side, not default

Remove "hidden from list queries by default" language from proto
comments and CLI help. Archived launch plans are not automatically
excluded from list results — callers must add a ne(state,2) filter.

Signed-off-by: Blake Naccarato <blake.naccarato@gmail.com>
Signed-off-by: Blake <blaketastic2@gmail.com>

Author: blaketastic2

flytectl/cmd/update/launch_plan.go

@@ -28,9 +28,9 @@ Deactivates a ` + "`launch plan <https://docs.flyte.org/en/latest/user_guide/pro
 
  flytectl update launchplan -p flytesnacks -d development core.control_flow.merge_sort.merge_sort --version v1 --deactivate
 
-Archives a launch plan version, marking it as old/unused. Archived launch plans are hidden from list
-queries by default and any active schedule is disabled. Archived launch plans can still be used to
-launch executions:
+Archives a launch plan version, marking it as old/unused. Archived launch plans can be filtered out
+of list queries using ne(state,2) and any active schedule is disabled. Archived launch plans can
+still be used to launch executions:
 ::
 
  flytectl update launchplan -p flytesnacks -d development core.control_flow.merge_sort.merge_sort --version v1 --archive

flyteidl/clients/go/assets/admin.swagger.json

@@ -40,8 +40,8 @@ message LaunchPlanCreateResponse {
 enum LaunchPlanState {
     INACTIVE = 0;
     ACTIVE = 1;
-    // Archived launch plans are considered old/unused and can be filtered out of list queries.
-    // Archiving a launch plan also disables any active schedule.
+    // Archived launch plans are considered old/unused and can be excluded from list queries
+    // using a ne(state,2) filter. Archiving a launch plan also disables any active schedule.
     // An archived launch plan can still be used to launch executions.
     ARCHIVED = 2;
 }