Put sriov-network-config-daemon contianer on the first place

[e0ne]

Make sriov-network-config-daemon container as a default to access logs easier without specifing container name. It's more often use-case rather then checking CNIs logs.

[github-actions]

Thanks for your PR,
To run vendors CIs use one of:

• /test-all: To run all tests for all vendors.
• /test-e2e-all: To run all E2E tests for all vendors.
• /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs use one of:

• /skip-all: To skip all tests for all vendors.
• /skip-e2e-all: To skip all E2E tests for all vendors.
• /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
  Best regards.

[coveralls]

Pull Request Test Coverage Report for Build 4542920865

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 9 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.1%) to 25.513%

---

Files with Coverage Reduction	New Missed Lines	%
api/v1/helper.go	3	41.32%
controllers/sriovnetwork_controller.go	6	61.9%

Totals
Change from base Build 4502357889:	-0.1%
Covered Lines:	1927
Relevant Lines:	7553

---

💛 - Coveralls

[tariq1890]

Instead of re-ordering the container part in the manifest, you can set the annotation to specify which container to default to when executing kubectl log/port-forward.

kubectl.kubernetes.io/default-container

[adrianchiris]

Thanks @e0ne !

im fine with both approaches (annot as @tariq1890 mentioned or reorder containers).

current approach ultimately ends up in fewer lines of text so thats a plus :) while the other is explicit so its clear what logs we are getting by default.