feat: add support for .obj files in memap

[vidavidorra]

Description

Add support for .obj files in memap tool. CMake/gcc-arm-none-eabi builds generate .obj files so this allows those builds to use the memap tool as well.

Pull request type

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

Reviewers

@theotherjimmy

Release Notes

• A brief description of changes introduced.
  Add support for .obj files in memap tool.
• An analysis of effects: components affected, potential consequences for users and reasons for the addition or change.
  Affects tools component, behaviour doesn't change for existing users. This adds support for using the memap tool for CMake/gcc-arm-none-eabi builds (and maybe others too).
• Migration guidance: actions for updating the current code. Please include code snippets to illustrate before and after the addition or change.
  N/A

[ciarmcom]

@vidavidorra, thank you for your changes.
@theotherjimmy @ARMmbed/mbed-os-tools @ARMmbed/mbed-os-maintainers please review.

[theotherjimmy]

I like that you added support for ARM and IAR to produce .obj files as well

[vidavidorra]

I like that you added support for ARM and IAR to produce .obj files as well

@theotherjimmy Haha, I take it those don't create .obj files 😄
I only use GCC_ARM and with that I ran into this issue. If ARM and IAR don't produce .obj, I can remove those parts. After all, no need to have that option in there if they don't produce such file(s).

[theotherjimmy]

@vidavidorra This allows us to add a cmake_arm or cmake_iar without any need to update memap too, so I say we keep it.

[cmonr]

CI started

[mbed-ci]

Test run: SUCCESS

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