Update pre-commit and run for all files

[sadikkuzu]

$ pre-commit run -a
check for added large files..............................................Passed
check for case conflicts.................................................Passed
check that executables have shebangs.....................................Passed
check json...............................................................Failed
- hook id: check-json
- exit code: 1

turbo.json: Failed to json decode (Expecting ',' delimiter: line 9 column 7 (char 188))

check for merge conflicts................................................Passed
check that scripts with shebangs are executable..........................Passed
check for broken symlinks............................(no files to check)Skipped
check toml...............................................................Passed
check xml................................................................Passed
check yaml...............................................................Passed
detect private key.......................................................Passed
fix end of files.........................................................Failed
- hook id: end-of-file-fixer
- exit code: 1
- files were modified by this hook

Fixing packages/web/public/stars.svg
Fixing packages/web/public/brand/positive-1080x1080.svg
Fixing packages/web/public/brand/negative-1920x1080.svg
Fixing packages/web/public/brand/positive-1920x1080.svg
Fixing packages/web/public/brand/negative-1080x1080.svg

fix utf-8 byte order marker..............................................Passed
forbid new submodules................................(no files to check)Skipped
mixed line ending........................................................Passed

[vercel[bot]]

@sadikkuzu is attempting to deploy a commit to the acik yazilim Team on Vercel.

A member of the Team first needs to authorize it.

[sadikkuzu]

In CI.yaml / Build and Test, how can we overcome the following error?:

[eser]

In CI.yaml / Build and Test, how can we overcome the following error?:

Actually, I'm still working on this issue. I didn't figure out its reason.