Remove nix

[dfarr]

Nix obscured the fact that our linter was out-of-date so this PR update the linter and includes a bunch of linting fixes.

[avillega]

I remember there is a way to use the artifacts of the build step. That way we don't need to build twice. We can do it on different PR

[dfarr]

Yes we can use the cache, but also agree, different PR

[codecov]

Codecov Report

Attention: Patch coverage is 48.14815% with 70 lines in your changes missing coverage. Please review.

Project coverage is 52.14%. Comparing base (3ff2ac1) to head (604fc8d).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/promises/promises.go	0.00%	24 Missing ⚠️
cmd/schedules/schedules.go	0.00%	22 Missing ⚠️
cmd/projects/scaffold.go	0.00%	6 Missing ⚠️
internal/app/subsystems/api/http/task.go	0.00%	3 Missing ⚠️
internal/util/util.go	25.00%	2 Missing and 1 partial ⚠️
test/dst/bc_validator.go	0.00%	3 Missing ⚠️
cmd/dst/issue.go	0.00%	2 Missing ⚠️
internal/app/coroutines/createPromise.go	83.33%	2 Missing ⚠️
test/dst/validator.go	33.33%	0 Missing and 2 partials ⚠️
cmd/projects/projects.go	0.00%	1 Missing ⚠️
... and 2 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #676      +/-   ##
==========================================
- Coverage   52.25%   52.14%   -0.12%     
==========================================
  Files         133      133              
  Lines       14409    14442      +33     
==========================================
+ Hits         7530     7531       +1     
- Misses       6418     6448      +30     
- Partials      461      463       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[lucperkins]

@dfarr @avillega As the person who set up Nix in this repo (as a favor for some old industry pals), I'd love to know in which ways it didn't meet your needs!

[avillega]

Hey @lucperkins. We don't think our project benefits from Nix, it is a simple Go project without many dependencies, on the other hand we were getting slowed down by nix, no one in the team is proficient in nix and any change that required updating our small set of dependencies was taking way longer than what we wanted. Without nix we can let dependabot take care of those. Basically the extra complexity was not worth it based on our project needs.

[lucperkins]

@avillega Makes sense, thanks for the explanation!