Add CNN class for MNIST dataset (✓ Sandbox Passed)

[sweep-nightly[bot]]

Description

This pull request adds a new CNN class for the MNIST dataset. It also updates the main.py file to use the new CNN class and the train function from the cnn.py file.

Summary

• Added CNN class in cnn.py file
• Updated main.py file to use the new CNN class and train function

Fixes #9.

---

🎉 Latest improvements to Sweep:

• Sweep now uses the rope library to refactor Python! Check out Large Language Models are Bad at Refactoring Code. To have Sweep refactor your code, try sweep: Refactor <your_file>.py!
• Sweep finds and fixes bugs in your code by writing unit tests! Check out Having GPT-4 Iterate on Unit Tests like a Human.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-nightly[bot]]

Sandbox Executions

• [X] Ran sandbox for src/cnn.py. ✓

  Sandbox logs for https://github.com/sweepai/evals/commit/6f6638f69035db64be8e1f2cfb81e5288000138e

trunk fmt src/cnn.py || exit 0 1/2 ✓

 ✔ Formatted src/cnn.py
Re-checking autofixed files...

Checked 1 file
✔ No issues

trunk check --fix --filter=-ruff --print-failures src/cnn.py 2/2 ✓

Checked 1 file
✔ No issues
Run trunk upgrade to upgrade 1 linter

• [X] Ran sandbox for src/main.py. ✓

  Sandbox logs for https://github.com/sweepai/evals/commit/efdeda6b44dc8f640ec4dcc257ddf0ed836a5419

trunk fmt src/main.py || exit 0 1/2 ✓

 ✔ Formatted src/main.py
Re-checking autofixed files...

 ✔ Formatted src/main.py
Re-checking autofixed files...

Checked 1 file
✔ No issues
Run trunk upgrade to upgrade 1 linter

trunk check --fix --filter=-ruff --print-failures src/main.py 2/2 ✓

Checked 1 file
✔ No issues

• [X] Ran sandbox for src/api.py. ✗

  Run `src/api.py` through the sandbox.

[sweep-nightly[bot]]

Apply Sweep Rules to your PR?

• [ ] Apply: All docstrings and comments should be up to date.
• [ ] Apply: Code should be properly formatted and indented.
• [ ] Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• [ ] Apply: Imports should be organized and grouped together.
• [ ] Apply: There should be no unused imports or variables.
• [ ] Apply: Code should be properly commented and include docstrings for functions and classes.