Skip Bare Metal green tea test for Network component

[rajkan01]

Description (required)

Net socket, Lora, Cellular,Network test cases require RTOS and will not run in bare metal so added MBED_CONF_RTOS_PRESENT guard to all test cases to skip.

Summary of change (What the change is for and why)

1.Net socket, Lora, Cellular, Network test cases use RTOS functionality(threads, APIs) so this test case cant run in bare-metal

1. Even if the main test case file main.cpp has MBED_CONF_RTOS_PRESENT guard still green tea test framework build all the depend on c or cpp files related to that test case which creates build issue.
2. Added the MBED_CONF_RTOS_PRESENT guard to all main test case files and dependency files as well to skip in the build.

• Note: These changes are done as identified that the network component uses RTOS API and not a very detailed analysis of the component.

3. Tested the green tea test on below list of targets with bare metal config and added the logs in
   IOTCORE-1397[https://jira.arm.com/browse/IOTCORE-1397] Jira ticket

• K64F
• K66F
• Nucleo F429ZI
• Nucleo F411RE
• Nucleo L073RZ
• Nucleo F207ZG

4. A main green tea test framework and mbed-os test cases change for bare metal is available in PR Bare metal greentea support #11721

Documentation (Details of any document updates required)

---

Pull request type (required)

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results (required)

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers (optional)

@AnttiKauppila @michalpasztamobica @evedon @jamesbeyond

---

Release Notes (required for feature/major PRs)

Summary of changes

Impact of changes

Migration actions required

[michalpasztamobica]

If we cannot use test filtering by name, which is available in the mbed test command, then I don't have any better idea on how to accomplish CI runs for bare metal...

[jamesbeyond]

LGTM now

[rajkan01]

@adbridge @0xc0170 please start the CI

[0xc0170]

CI started

[mbed-ci]

Test run: FAILED

Summary: 1 of 5 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_greentea-test