Add CI to enforce one sentence per CR/LF

[markcmiller86]

All of our text processing tools (including most of the high quality diffing and auto-merging tools) operate on the quanta of a single line of text (delimited typically by carriage-return/line-feed chars). This is crticial as it effects many aspects of GitHub workflows and GitHub.com features like suggesting changes, how likely two authors working on the same file will create merge conflicts, how easily patch files can be created and applied, etc. Don't take my word for it. See these notes, originally suggested by @bartlettroscoe.

We all write our code according to this rule. When we write code, we do NOT do this...

#include <stdio.h> int main() { printf("Hello, world!\n"); for(int i = 0; i < 5; i++) { printf("%d ", i); } return 0; }

We DO, do this...

#include <stdio.h>

int main() {
    printf("Hello, world!\n");
    for(int i = 0; i < 5; i++) {
        printf("%d ", i);
    }
    return 0;
}

Can we please agree to adding some CI to ensure our prose follows this same basic rule as well?

[bartlettroscoe]

I wonder how robust such as check would be? I mean, periods, question marks, etc. can appear in the middle of a sentience in some cases (such as 'i.e.', 'e.g.', etc.).

[rinkug]

The check would be good.
I forget all the time.
EB docs should have this change too right?

@markcmiller86 : If you have time to delver deeper and do it, then please go ahead (Thanks!). Else put the existing label of "postoned for future"