Use CI runners for integration tests

Author: yhaliaw

.github/workflows/integration_test.yaml

@@ -23,7 +23,7 @@ jobs:
       modules: '["test_charm_metrics_failure", "test_charm_metrics_success", "test_charm_fork_repo", "test_charm_fork_path_change", "test_charm_no_runner", "test_charm_runner", "test_debug_ssh", "test_charm_upgrade",  "test_reactive", "test_jobmanager_prespawned", "test_jobmanager_reactive"]'
       extra-arguments: '-m openstack --log-format="%(asctime)s %(levelname)s %(message)s"'
       self-hosted-runner: true
-      self-hosted-runner-label: stg-private-endpoint
+      self-hosted-runner-label: self-hosted-linux-amd64-noble-pfe-ci 
   openstack-integration-tests-cross-controller-private-endpoint:
     name: Cross controller integration test using private-endpoint
     uses: canonical/operator-workflows/.github/workflows/integration_test.yaml@main
@@ -36,7 +36,7 @@ jobs:
       modules: '["test_prometheus_metrics"]'
       extra-arguments: '-m openstack --log-format="%(asctime)s %(levelname)s %(message)s"'
       self-hosted-runner: true
-      self-hosted-runner-label: stg-private-endpoint
+      self-hosted-runner-label: self-hosted-linux-amd64-noble-pfe-ci
   allure-report:
     if: ${{ (success() || failure()) && github.event_name == 'schedule' }}
     needs: