Drop include paths for ARM assembler

[theotherjimmy]

Description

The arm assembler would include many, many include paths on the command
line corresponding to anywhere it's possible to locate a header file.
This caused the following problem in uvision:

assembling startup_nrf52832.S...
startup_nrf52832.S: error: A3907U: Via file
'.\build\startup_nrf52832._ia' command too long for buffer.

We work around this issue by dropping the include paths from the
assembler in both mbed compile and mbed export. This has the
advantage that it's consistent with IAR.

Pull request type

[X] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change

[cmonr]

/morph build

[mbed-ci]

Build : FAILURE

Build number : 1828
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/6713/

[0xc0170]

This actually reverts ebc9289 and solves the problem @hug-dev was having by updating the path in targets/TARGET_ARM_SSG/TARGET_CM3DS_MPS2/device/TOOLCHAIN_ARM_STD/startup_MPS2.S ? The include is still there, where does assembler finds it? - not clear to me.

[0xc0170]

@hug-dev Please review

[hug-dev]

This is fine for me, as long as the preprocessor is called on the assembly file. I don't see the structure of files changing anytime soon so this is fine using relative path.

[0xc0170]

Please review the build failures (similar are in jenkins CI)

[theotherjimmy]

That should fix it.

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 1881
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/6713/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[mbed-ci]

Test : SUCCESS

Build number : 1695
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/6713/1695

[mbed-ci]

Exporter Build : SUCCESS

Build number : 1530
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/6713/