Remove CTCOMPATIBLE mode

[N0NB]

I first broached this subject back in November 2019:

https://lists.nongnu.org/archive/html/tlf-devel/2019-11/msg00120.html

I'd found that the CT commands in Tlf were not correct but since no one had ever complained, I corrected them. No one complained about the changed behavior which led to this thread in January 2020:

https://lists.nongnu.org/archive/html/tlf-devel/2020-01/msg00003.html

One objection was posted by Fred, DH5FS:

https://lists.nongnu.org/archive/html/tlf-devel/2020-01/msg00010.html

Questions were asked of Fred with no response. In May 2020 I followed up the thread with:

https://lists.nongnu.org/archive/html/tlf-devel/2020-05/msg00008.html

Still no word from Fred.

I will make one more post to the mailing list on this and if there is no opposition, CTCOMPATIBLE will be removed. I think there is enough capability in Tlf to warrant moving on from what is now essentially a dead and gone way of logging.

[N0NB]

I followed up again in this thread in August 2023:

https://lists.gnu.org/archive/html/tlf-devel/2023-08/msg00003.html

and again Fred stated that removal would leave him with no way to do an XMAS sprint. Repeated questions on use of the SPRINTMODE key word as a way to resolve his objection went unanswered.

It has now been so long that I forgot what I had in mind except simply removing everything that gets invoked when CTCOMPATIBLE is used.

[df7cb]

Fwiw I'm just staring at the code flow in src/getexchange.c and there are lots of ctcomp warts that look very icky.

I was starting here and trying to figure out where the logging actually happens:

https://github.com/Tlf/tlf/blob/e3b7cb888bdac96ffee585d6f847535e6114110c/src/getexchange.c#L320-L334

I'll all for removing this mode.