Remove non-default, memory-heavy tests from the benchmark application

[k-stachowiak]

This PR removes memory-heavy tests from the benchmark application. They are not used by default and they don't work for all the tested devices due to the memory restrictions (at least ones implied by the build configurations).

Fixes (works around until we have resolved the memory configuration issues) #138

edit:
It apparently also fixes (works around...) #208 and #210.

[k-stachowiak]

retest

[k-stachowiak]

retest

[k-stachowiak]

The only failing tests are due to a known issue: #209

[andresag01]

@k-stachowiak: Thanks for the PR, but in my opinion this is not sufficient. I think you should explicitly use #undef if you want that particular feature to be disabled.

[k-stachowiak]

@andresag01 Thanks for the review.

This change was made based on the following reasoning: there are some features used here, that are not even enabled by default. Therefore, we should not enable them forcibly. Should, in the future, the features become enabled by default (and break this app), we may return to this issue, and e.g. explicitly disable them.

Looking at this from another perspective, there are probably more features in Mbed TLS that would break the benchmark, but we don't explicitly disable the in this file, since they are not enabled by default. Should DHM be treated specially in this case?

Please consider my arguments and confirm, if you think the feature should still be explicitly disabled.

[andresag01]

ok

[k-stachowiak]

@andresag01 Do you feel satisfied by my reply to your comment? If so, can you approve the PR, or maybe you have more change requests?

[simonbutcher]

Passes CI with the exception of the known broken tests on UBLOX.

[adbridge]

@k-stachowiak @sbutcher-arm Why has this just been merged to master when the 5.11 release has not been made yet and all fixes should consequently still be going to the 5.11.0-oob branch ??!!