Update Cypress Targets and Assets

[dustin-crossman]

Summary of changes

Update Cypress targets with latest tools/PDL library.
Update PSoC6 core_lib.
Update PSoC6 abstraction rtos.
Update PSoC6 PDL to version 1.4.0

Impact of changes

Migration actions required

Documentation

None

---

Pull request type

[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

[] 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

GT_FT_KIT_062_BLE_GCC.txt
GT_FT_KIT_062S2_43012_GCC.txt
GT_FT_KIT_EVB_43012_GCC.txt
GT_FT_P6S1_43012EVB_01_GCC.txt
GT_FT_KIT_062_WIFI_BT_GCC.txt
GT_FT_PROTO_063_BLE_GCC.txt
GT_FT_PROTO_062_4343W_GCC.txt
GT_FT_PROTO_062S3_4343W.txt
GT_FT_P6S1_43438EVB_01_GCC.txt

Network tests:
GT-FT-KIT_062_WIFI_BT-GCC-NET.txt
GT-FT-KIT-062S2-43012-GCC-NET.txt
GT-FT-PROT-062-4343W-GCC-NET.txt
GT_FT_KIT_EVB_43012_GCC-NET.txt
GT_FT_P6S1_43438EVB_01_GCC_NET.txt

Test failures and explanations:

• The pinmap test failure on the CYW9P6S21_43012EVB_01 is caused because 2 of the ARDUINO pins on that board are not connected. This is being evaluated for proper resolution in a future PR.
• Kvstore failures on the CY8CPROTO_063_BLE were fixed by applying Improve reliability of KVStore general tests #12060.
• The mbed_drivers timeout test failure seen on the CY8CPROTO_062_4343W is an intermittent failure seen occasionally on multiple boards. It is a bug in the test that will be addressed in a future PR.
• All sleep failures are expected due to to a known incompatibility between the sleep tests and our UART driver.

---

Reviewers

---

[ciarmcom]

@dustin-crossman, thank you for your changes.
@maclobdell @ARMmbed/mbed-os-maintainers please review.

[bulislaw]

Simmed through the changes, nothing raised any flags.

[0xc0170]

@dustin-crossman Can you add details to the commits what updates are we getting.

Usually this reflects the version (released or internal at least), to keep track what version we have. If updates in this PR are not versioned, at least information about what we are updating.

The description above contains some versions, they should be in the commits as well.

[dustin-crossman]

@0xc0170 Fixed up commit messages!

[0xc0170]

CI started

[mbed-ci]

Test run: FAILED

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

Failed test jobs:

• jenkins-ci/mbed-os-ci_dynamic-memory-usage

[0xc0170]

I restarted dynamic memory usage, we might having an issue there (not related to this PR).

cc @VeliMattiLahtela