Tools: Detect Arm Compiler version using Component

[theotherjimmy]

Description

In an offline discussion, I found that the arm compiler may spit out:

Product: MDK Professional 5.22
Component: ARM Compiler 5.06 update 6 (build 750)

instead of what I was expecting.

This PR fixes detection logic to use the component field instead of
the product field like I was using before.

Pull request type

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

[theotherjimmy]

@jeromecoutant Could you verify this fix?

[cmonr]

LGTM, will hold for @jeromecoutant's Ok.

[jeromecoutant]

Hi

Issue fixed.

By the way, before this patch, why the error detection didn't stop test execution?

[theotherjimmy]

@jeromecoutant Thanks for testing!

For the "why not stop" you can see the original PR, #7247

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[mbed-ci]

Exporter Build : FAILURE

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

[mbed-ci]

Test : SUCCESS

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

[0xc0170]

/morph export-build

[mbed-ci]

Exporter Build : FAILURE

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

[0xc0170]

/morph export-build

[mbed-ci]

Exporter Build : FAILURE

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

[0xc0170]

/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

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