Fix getting-started guide and network traffic plugin wrappers

- Update getting-started.md to use full paths for YAML files from repo root
- Fix kubeconfig references to use kubeplus-saas-provider.json (actual file created)
- Add CRD wait step before creating HelloWorldService instances
- Fix kubectl-allow-network-traffic and kubectl-deny-network-traffic wrappers
  to properly handle -k flag by reordering arguments for argparse compatibility
- Add -k flag back to allow/deny commands in getting-started guide

This allows users to run all commands from the repository root without
needing to change directories, and ensures the -k flag works correctly
as documented in kubectl-kubeplus-commands help text.

Author: anniegracehu

examples/getting-started.md

@@ -192,7 +192,7 @@ kubectl create -f examples/multitenancy/hello-world/hs2.yaml --kubeconfig=kubepl
 In some scenarios, you might want to enable controlled communication between instances running in different namespaces. KubePlus provides a custom kubectl plugin for this purpose. To allow bi-directional traffic between the two HelloWorldService instances (deployed in namespaces `hs1` and `hs2`), run:
 
 ```sh
-kubectl allow network traffic hs1 hs2
+kubectl allow network traffic hs1 hs2 -k kubeplus-saas-provider.json
 ```
 
 ```sh 
@@ -216,7 +216,7 @@ The connection should be allowed
 To deny the traffic between namespace 
 
 ```sh
-kubectl deny network traffic hs1 hs2
+kubectl deny network traffic hs1 hs2 -k kubeplus-saas-provider.json
 ```
 
 ```sh 

plugins/kubectl-allow-network-traffic

@@ -2,5 +2,20 @@
 
 source utils.sh  # if you have common utility functions; else remove this line
 
-# This wrapper passes all arguments to our Python script.
-python3 "$KUBEPLUS_HOME/plugins/network_traffic.py" allow "$@"
+# Usage (as advertised in kubectl-kubeplus-commands):
+#   kubectl allow network traffic <ns1> <ns2> [-k <kubeconfig>]
+#
+# kubectl will translate that to the plugin name:
+#   kubectl-allow-network-traffic <ns1> <ns2> [-k <kubeconfig>]
+#
+# Here we:
+#   - Take the first two positional args as namespaces
+#   - Pass any remaining args (e.g. -k <kubeconfig>) as global options
+#   - Reorder so global options come before the subcommand for argparse
+
+ns1="$1"
+ns2="$2"
+shift 2
+
+# "$@" now contains any remaining flags (e.g. -k kubeplus-saas-provider.json)
+python3 "$KUBEPLUS_HOME/plugins/network_traffic.py" "$@" allow "$ns1" "$ns2"

plugins/kubectl-deny-network-traffic

@@ -2,5 +2,20 @@
 
 source utils.sh  # if you have common utility functions; else remove this line
 
-# This wrapper passes all arguments to our Python script.
-python3 "$KUBEPLUS_HOME/plugins/network_traffic.py" deny "$@"
+# Usage (as advertised in kubectl-kubeplus-commands):
+#   kubectl deny network traffic <ns1> <ns2> [-k <kubeconfig>]
+#
+# kubectl will translate that to the plugin name:
+#   kubectl-deny-network-traffic <ns1> <ns2> [-k <kubeconfig>]
+#
+# Here we:
+#   - Take the first two positional args as namespaces
+#   - Pass any remaining args (e.g. -k <kubeconfig>) as global options
+#   - Reorder so global options come before the subcommand for argparse
+
+ns1="$1"
+ns2="$2"
+shift 2
+
+# "$@" now contains any remaining flags (e.g. -k kubeplus-saas-provider.json)
+python3 "$KUBEPLUS_HOME/plugins/network_traffic.py" "$@" deny "$ns1" "$ns2"