Removed cymetadata section from FUTURE_SEQUANA targets

[lrusinowicz]

Description

This data, placed at physically not existing addresses (0x9xxxxxxx) was used
only by PSoC Programmer and KitProg2 and is no longer needed, but was causing
issues with standard hex file processing tools like srecord (srec_cat).

@0xc0170
This should remove nightly exporter failures (#9611).

Pull request type

[x] Fix
[ ] Refactor
[x] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

Release Notes

[orenc17]

@lrusinowicz could you please also update the FUTURE_SEQUANA_PSA secure images with
python tools/psa/release.py -m FUTURE_SEQUANA_M0_PSA

[0xc0170]

@lrusinowicz could you please also update the FUTURE_SEQUANA_PSA secure images with
python tools/psa/release.py -m FUTURE_SEQUANA_M0_PSA

New PR or here? Just to know when to start CI for this one

[lrusinowicz]

@orenc17
The script you've mentioned fails for me with

$ python tools/psa/release.py -m FUTURE_SEQUANA_M0_PSA
Traceback (most recent call last):
  File "tools/psa/release.py", line 163, in <module>
    main()
  File "tools/psa/release.py", line 159, in main
    build_psa_platform(target, toolchain)
  File "tools/psa/release.py", line 120, in build_psa_platform
    if _psa_backend(options.mcu) is 'TFM':
NameError: global name 'options' is not defined

I might not be on proper master commit for it. Anyway, as exporters should stop failing even with old images I would rather wait for merge and then update images from clean master.

[orenc17]

@lrusinowicz this error is fixed in the latest master
you create the secure binaries in a later PR

[0xc0170]

CI started

[mbed-ci]

Test run: SUCCESS

Summary: 13 of 13 test jobs passed
Build number : 1
Build artifacts

[ghost]

Meets criteria, fix for target to support PSA. Approved.