Proposal: Remove options to disable std C library

[thetic]

As best I can tell, this functionality has rotted. I don't think it is feasible or responsible to attempt to maintain functionality that is not under test. I think repair/test would require some significant redesign. As such I propose to remove it outright.

Closes #1656.

[coveralls]

Coverage remained the same at 99.64% when pulling 503de82 on thetic:no-no-std-c into 8cc621c on cpputest:master.

[basvodde]

I don't really want to remove the feature as it is used when using CppUTest in e.g. Linux kernel development. That is when we added it.

[thetic]

Is there a version known to work or are there special instructions for testing it? I'd like to get it in CI if we want to keep it.

[basvodde]

The main thing is to keep the compiling in the CI. When that is in there then it isn't possible to include StdC headers directly without failing the build. So keeping that build then prevents regression. Then when people want to use CppUTest on kernel development or embedded development that has no stdC then they just need to implement the PlatformSpecific functions.

I have been thinking to try to implement some of the PlatformSpecific functions in an as much platform independent way (such as having a printf implementation) but haven't ever gotten to it and not sure it will actually be worth it.

[thetic]

I understand how to test that it builds, but how do we test that it works?

[thetic]

Let's continue discussion on #1656