fix: gocritic linter issues

[alexandear]

Description

This PR enables gocritic linter and fixes the following linter issues:

❯ ./bin/golangci-lint run
pkg/database/handler.go:81:4: exitAfterDefer: log.Fatal will exit, and `defer rows.Close()` will not run (gocritic)
                        log.Fatal(err)
                        ^
pkg/cache/lrucache_test.go:41:3: assignOp: replace `i = i + 1` with `i++` (gocritic)
                i = i + 1
                ^
pkg/providers/cache.go:44:46: captLocal: `URL' should not be capitalized (gocritic)
func (lc *LRUCacheGitRepoProvider) FetchRepo(URL string) (GitRepo, error) {
                                             ^
pkg/providers/memory.go:26:46: captLocal: `URL' should not be capitalized (gocritic)
func (im *InMemoryGitRepoProvider) FetchRepo(URL string) (GitRepo, error) {
                                             ^
pkg/server/server.go:62:2: exitAfterDefer: log.Fatal will exit, and `defer p.Logger.Sync()` will not run (gocritic)
        log.Fatal(http.ListenAndServe(fmt.Sprintf(":%s", serverPort), nil))
        ^

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

Updates #49

log.Fatal mistake was found by reading the article https://dev.to/opensauced/how-we-made-our-go-microservice-24x-faster-5h3l

Mobile & Desktop Screenshots/Recordings

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📓 docs.opensauced.pizza
• 🍕 dev.to/opensauced
• 📕 storybook
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

[github-actions]

Congrats on making your first Pull Request and thanks for taking the time to improve Open Sauced! ❤️! 🎉🍕
Say hello by joining the conversation in our Discord

[jpmcb]

Hi @alexandear - very solid!! 👏🏼 Thanks so much for the contribution!!

[OgDev-01]

🍕

[nickytonline]

🚀