BL mode: Prevent jump address conflicts

[theotherjimmy]

Description

The Intel hex file format contains enough information to load a program
into memory and begin it's execution. This includes a jump address,
which is generally set to main, that is generated by most compilers. When
merging two Intel hex files, there is no way to know a priori which one
is the true jump address. Therefore, IntelHex (the python package) has
opted to raise an exception: Starting addresses are different. This can
happen when jump address is set in a boot loader and an application; when
both are built as Intel hex. This patch removes jump addresses before
merging the boot loader with the application.

Pull request type

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

[theotherjimmy]

That is possibly the longest explanation I have had for adding one line of code.

[dlfryar-zz]

+1 verified with latest code in mbed-os/master, mbed-bootloader/v3.3.0, and mbed-cloud-client-example/1.3.1.1 on the Nordic NRF52840_DK

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : SUCCESS

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

[mbed-ci]

Test : SUCCESS

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