Remove unsupported integration tests from workflows

[ljkiraly]

The following tests can be removed from any workflow and can be archived:

• integration-k8s-aks - requires access to Azure Cloud Service.
• integration-k8s-aws - requires access to Amazon Elastic Kubernetes Service. Fails since five month. Access details to be clarified.
• integration-interdomain-k8s - requires access to gke, aks, aws. Runs interdomain tests

The suite set for integration-k8s-aks, integration-k8s-aws and integration-k8s-gke (this one runs successfully on Google's Kubernetes Engine):

• features.Suite
• basic.Suite
• afxdp.Suite
• memory.Suite
• heal.Suite
• observability.Suite

There is no special suite which is only covered by integration-k8s-aks, integration-k8s-aws test runs.

• integration-k8s-packet - requires access to Equinix Metal servers which supports melanox for sriov tests. Last succesfull run more then 8 month ago. Runs on default k8s CNI and Calico environments.

The suite set for integration-k8s-packet (default CNI):

• features.Suite
• sriov_vlantag.Suite
• multiforwarder_vlantag.Suite
• basic.Suite
• ipsec_mechanism.Suite
• memory.Suite
• heal.Suite
• observability.Suite

The suite set for integration-k8s-packet (Calico):

• features.Suite without TestMutually_aware_nses
• sriov.Suite
• multiforwarder.Suite
• memory.Suite
• heal.Suite
• observability.Suite

The sriov_vlantag, sriov, multiforwarder and multiforwarder_vlantag suites run by integration-k8s-packet only. The integration test can be removed from workflows, but removal of sriov support can be handled separately.

[huly-github-staging]

Connected to Huly®: NETWO-20957