tidy-up: mostly whitespace nits

- delete completed TODO from `./CMakeLists.txt`.
- convert a C++ comment to C89 in `./CMake/CurlTests.c`.
- delete duplicate EOLs from EOF.
- add missing EOL at EOF.
- delete whitespace at EOL (except from expected test results).
- convert tabs to spaces.
- convert CRLF EOLs to LF in GHA yaml.
- text casing fixes in `./CMakeLists.txt`.
- fix a codespell typo in `packages/OS400/initscript.sh`.

Closes #11772

docs/BUFQ.md

@@ -28,9 +28,8 @@ To pass data into a `bufq` without an extra copy, read callbacks can be used.
 typedef ssize_t Curl_bufq_reader(void *reader_ctx, unsigned char *buf, size_t len,
                                  CURLcode *err);
 
-ssize_t Curl_bufq_slurp(struct bufq *q, Curl_bufq_reader *reader, void *reader_ctx, 
+ssize_t Curl_bufq_slurp(struct bufq *q, Curl_bufq_reader *reader, void *reader_ctx,
                         CURLcode *err);
-
 ```
 
 `Curl_bufq_slurp()` will invoke the given `reader` callback, passing it its own internal
@@ -44,7 +43,7 @@ The analog mechanism for write out buffer data is:
 typedef ssize_t Curl_bufq_writer(void *writer_ctx, const unsigned char *buf, size_t len,
                                  CURLcode *err);
 
-ssize_t Curl_bufq_pass(struct bufq *q, Curl_bufq_writer *writer, void *writer_ctx, 
+ssize_t Curl_bufq_pass(struct bufq *q, Curl_bufq_writer *writer, void *writer_ctx,
                        CURLcode *err);
 ```
 
@@ -106,10 +105,10 @@ If a `bufq` is created with a `bufc_pool`, the no longer used chunks are returne
 
 ## empty, full and overflow
 
-One can ask about the state of a `bufq` with methods such as `Curl_bufq_is_empty(q)`, 
+One can ask about the state of a `bufq` with methods such as `Curl_bufq_is_empty(q)`,
 `Curl_bufq_is_full(q)`, etc. The amount of data held by a `bufq` is the sum of the data in all its chunks. This is what is reported by `Curl_bufq_len(q)`.
 
-Note that a `bufq` length and it being "full" are only loosely related. A simple example: 
+Note that a `bufq` length and it being "full" are only loosely related. A simple example:
 
 * create a `bufq` with chunk_size=1000 and max_chunks=4.
 * write 4000 bytes to it, it will report "full"
@@ -140,5 +139,3 @@ A pool can be shared between many `bufq`s, as long as all of them operate in the
 
 * when all `bufq`s are empty, only memory for `max_spare` chunks in the pool is used. Empty `bufq`s will hold no memory.
 * the latest spare chunk is the first to be handed out again, no matter which `bufq` needs it. This keeps the footprint of "recently used" memory smaller.
-
-

docs/BUGS.md

@@ -199,7 +199,7 @@
 
 ## Not reproducible
 
- We may require further work from you who actually see or experience the 
+ We may require further work from you who actually see or experience the
  problem if we cannot reproduce it and cannot understand it even after having
  gotten all the info we need and having studied the source code over again.
 

docs/CONNECTION-FILTERS.md

@@ -1,6 +1,6 @@
 # curl connection filters
 
-Connection filters is a design in the internals of curl, not visible in its public API. They were added 
+Connection filters is a design in the internals of curl, not visible in its public API. They were added
 in curl v7.xx.x. This document describes the concepts, its high level implementation and the motivations.
 
 ## Filters
@@ -34,13 +34,13 @@ Direct:
   http://localhost/      conn -> cf-socket
   https://curl.se/       conn -> cf-ssl -> cf-socket
 Via http proxy tunnel:
-  http://localhost/      conn -> cf-http-proxy -> cf-socket 
+  http://localhost/      conn -> cf-http-proxy -> cf-socket
   https://curl.se/       conn -> cf-ssl -> cf-http-proxy -> cf-socket
 Via https proxy tunnel:
-  http://localhost/      conn -> cf-http-proxy -> cf-ssl -> cf-socket 
+  http://localhost/      conn -> cf-http-proxy -> cf-ssl -> cf-socket
   https://curl.se/       conn -> cf-ssl -> cf-http-proxy -> cf-ssl -> cf-socket
 Via http proxy tunnel via SOCKS proxy:
-  http://localhost/      conn -> cf-http-proxy -> cf-socks -> cf-socket 
+  http://localhost/      conn -> cf-http-proxy -> cf-socks -> cf-socket
 ```
 
 ### Connecting/Closing
@@ -50,7 +50,7 @@ Before `Curl_easy` can send the request, the connection needs to be established.
 Each filter does in principle the following:
 
 ```
-static CURLcode 
+static CURLcode
 myfilter_cf_connect(struct Curl_cfilter *cf,
                     struct Curl_easy *data,
                     bool *done)
@@ -63,7 +63,7 @@ myfilter_cf_connect(struct Curl_cfilter *cf,
   }
                                  /* Let the filters below connect */
   result = cf->next->cft->connect(cf->next, data, blocking, done);
-  if(result || !*done)    
+  if(result || !*done)
     return result;               /* below errored/not finished yet */
 
   /* MYFILTER CONNECT THINGS */  /* below connected, do out thing */

docs/DEPRECATE.md

@@ -46,4 +46,3 @@ curl will remove the support for space-separated names in July 2024.
  - Support for systems without 64 bit data types
  - NSS
  - gskit
-

docs/HTTP3.md

@@ -340,7 +340,7 @@ should be either in your PATH or your current directory.
 Create a `Caddyfile` with the following content:
 ~~~
 localhost:7443 {
-	respond "Hello, world! you are using {http.request.proto}"
+  respond "Hello, world! you are using {http.request.proto}"
 }
 ~~~
 

docs/HYPER.md

@@ -67,4 +67,3 @@ still need attention and verification include:
 - h2 Upgrade:
 - receiving HTTP/1 trailers
 - sending HTTP/1 trailers
-

docs/cmdline-opts/max-filesize.d

@@ -20,4 +20,4 @@ gigabytes. Examples: 200K, 3m and 1G. (Added in 7.58.0)
 
 **NOTE**: The file size is not always known prior to download, and for such
 files this option has no effect even if the file transfer ends up being larger
-than this given limit.
+than this given limit.

docs/cmdline-opts/variable.d

@@ -54,4 +54,3 @@ shows the content URL (percent) encoded.
 expands the variable base64 encoded
 .RE
 .IP
-

docs/examples/ipv6.c

@@ -60,4 +60,3 @@ int main(void)
 #endif
   return 0;
 }
-

docs/libcurl/libcurl-ws.3

@@ -112,4 +112,3 @@ change API, ABI and behavior before this "goes live".
 .BR curl_ws_meta "(3), " curl_ws_recv "(3), " curl_ws_send "(3), "
 .BR curl_easy_init "(3), " CURLOPT_CONNECT_ONLY "(3), "
 .BR CURLOPT_WRITEFUNCTION "(3)" CURLOPT_WS_OPTIONS "(3), "
-

docs/libcurl/opts/CURLOPT_HSTSREADFUNCTION.3

@@ -86,4 +86,3 @@ This returns CURLE_OK.
 .SH "SEE ALSO"
 .BR CURLOPT_HSTSREADDATA "(3), " CURLOPT_HSTSWRITEFUNCTION "(3), "
 .BR CURLOPT_HSTS "(3), " CURLOPT_HSTS_CTRL "(3), "
-

docs/libcurl/opts/CURLOPT_UPKEEP_INTERVAL_MS.3

@@ -80,4 +80,3 @@ Added in 7.62.0
 Returns CURLE_OK
 .SH SEE ALSO
 .BR CURLOPT_TCP_KEEPALIVE "(3), "
-

docs/libcurl/opts/Makefile.inc

@@ -348,7 +348,7 @@ man_MANS =                                      \
   CURLOPT_SSL_CIPHER_LIST.3                     \
   CURLOPT_SSL_CTX_DATA.3                        \
   CURLOPT_SSL_CTX_FUNCTION.3                    \
-  CURLOPT_SSL_EC_CURVES.3			\
+  CURLOPT_SSL_EC_CURVES.3                       \
   CURLOPT_SSL_ENABLE_ALPN.3                     \
   CURLOPT_SSL_ENABLE_NPN.3                      \
   CURLOPT_SSL_FALSESTART.3                      \