ci: remove --check flag from scarb fmt command

[AfroTechBoss]

The --check flag was removed to make the CI workflow actually format the code rather than just checking the formatting. This ensures consistent code style across the codebase.

Key points about this commit message:
1. Type is `ci` since it's modifying a GitHub workflow file
2. No scope needed as it's clear from context
3. Description explains what changed (removed --check flag) and why (to actually format code)
4. Body provides additional context about ensuring consistent code style
5. Ignores the bash.exe.stackdump file as it appears to be an accidental crash dump that shouldn't be committed


### Related Issues
- Closes #112 

[coxmars]

@AfroTechBoss delete this file

[jimenezz22]

@AfroTechBoss Why did you upload this file? It looks very strange and a bit malicious

[AfroTechBoss]

@AfroTechBoss Why did you upload this file? It looks very strange and a bit ma

[AfroTechBoss]

@AfroTechBoss Why did you upload this file? It looks very strange and a bit malicious

Hi @coxmars
The bash.exe.stackdump file is a debugging tool generated when the bash.exe process crashes, usually in a Windows environment using tools like Cygwin or MinGW. It contains a snapshot of the program's call stack at the moment of the crash, which helps developers diagnose the cause of the issue.
I didn't know I pushed along with the main changes. sorry about that.

I have removed it and pushed again.

[coxmars]

@AfroTechBoss Why did you upload this file? It looks very strange and a bit malicious

Hi @coxmars The bash.exe.stackdump file is a debugging tool generated when the bash.exe process crashes, usually in a Windows environment using tools like Cygwin or MinGW. It contains a snapshot of the program's call stack at the moment of the crash, which helps developers diagnose the cause of the issue. I didn't know I pushed along with the main changes. sorry about that.

I have removed it and pushed again.

Do not worry, thanks for the explanation sir 🫡