[v2] site status with disabled linkAccess type is not nice

[c-kruse]

Describe the bug This is a total nit - something that we can probably live with for some time.

When a site is configured with a link access type that is not enabled by the controller the site status is stuck at containers with unready status: [config-sync] even though the config-sync container seems fine to me.

[christian@rh ~]$ k get sites -A                                                                                                                                                                                                                                                                                                               [0/5503]
NAMESPACE         NAME              STATUS                                          SITES IN NETWORK
public-contour    public-contour    containers with unready status: [config-sync]   1
public-gw         public-gw         containers with unready status: [config-sync]   1
public-lb         public-lb         OK                                              1
public-nginx      public-nginx      containers with unready status: [config-sync]   1
public-nodeport   public-nodeport   containers with unready status: [config-sync]   1
[christian@rh ~]$ k get securedaccesses.skupper.io -A
NAMESPACE         NAME                   STATUS
public-contour    skupper-router-1       unsupported access type
public-gw         skupper-router-1       unsupported access type
public-lb         skupper-router-1       OK
public-nginx      skupper-router-1       unsupported access type
public-nodeport   skupper-router-1       unsupported access type
skupper           skupper-grant-server   OK

Maybe the securedaccess status should get bubbled up to the site?