[Fix] grammar HTTPS cloning, install.sh broken pipe on fzf/ripgrep, Windows line endings

[vasilaking]

Summary

Three independent bugs that together prevent a clean install on Linux
(especially from Windows/WSL), fixed and tested end-to-end.

---

Bug 1 — tsi clones grammars over SSH, failing for most users

File: ts/ts_lang_install.c

Grammar installation used git@github.com: SSH URLs, which require a
GitHub SSH key to be configured. This fails silently for any user who
hasn't set one up (the majority of users, and all fresh environments).

Public repos like tree-sitter grammars don't need SSH, HTTPS works
without any credentials.

Fix: Replaced git@github.com: with https://github.com/ in both
clone URL templates.

Tested: Ran tsi python with the newly built binary and confirmed
the clone line reads https:// with no authentication required:

---

Bug 2 — install.sh fails to install fzf and ripgrep

File: install.sh

The latest_tag() function piped curl directly into grep -m1:

$DL_STDOUT "https://api.github.com/repos/$1/releases/latest" \
    | grep -m1 '"tag_name"' \
    | sed -E '...'

grep -m1 exits after the first match, closing its end of the pipe
while curl is still downloading. Curl then fails with exit code 23
("Failure writing output to destination"). Because the script runs
under set -euo pipefail, this kills the entire function, and
fzf/ripgrep never install.

Fix: Capture the full response into a variable first, then grep
through it. Curl completes before grep ever runs, so no broken pipe:

latest_tag() {
    local json
    json=$($DL_STDOUT "https://api.github.com/repos/$1/releases/latest") || return 1
    printf '%s\n' "$json" \
        | grep -m1 '"tag_name"' \
        | sed -E 's/.*"tag_name"[[:space:]]*:[[:space:]]*"([^"]+)".*/\1/'
}

Tested: Confirmed fzf and ripgrep download and install successfully:

---

Bug 3 — Windows line endings break the build and install script

File: .gitattributes (added)

The repo had no .gitattributes, so Windows users cloning it received
\r\n line endings across all files. This caused:

• install.sh → /usr/bin/env: 'bash\r': No such file or directory
• compile_flags.txt → GCC received flags with trailing \r, producing
  errors like '; did you mean '-Wall'?
• All .c, .h, and makefile files were similarly affected

Fix: Added .gitattributes enforcing LF for all files:
* text=auto eol=lf

Tested: Verified clean build with make after line ending conversion
on a Windows-cloned copy of the repo:

...

successful wihtout errors

[halicea]

I'll just post one more change here for a https->ssh fallback.