Add Docker Compose Configuration for Prover Client

[MdTeach]

Description

• Added Docker Compose setup for running the prover client.
• Updated the Docker Compose README with instructions for running the prover.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature/Enhancement (non-breaking change which adds functionality or enhances an existing one)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor
• New or updated tests
• Dependency Update

Notes to Reviewers

Checklist

• I have performed a self-review of my code.
• I have commented my code where necessary.
• I have updated the documentation if needed.
• My changes do not introduce new warnings.
• I have added tests that prove my changes are effective or that my feature works.
• New and existing tests pass with my changes.

Related Issues

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.61%. Comparing base (d23d60a) to head (5546d28).
Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main     #664      +/-   ##
==========================================
+ Coverage   54.60%   54.61%   +0.01%     
==========================================
  Files         318      318              
  Lines       34067    34067              
==========================================
+ Hits        18603    18607       +4     
+ Misses      15464    15460       -4     

see 1 file with indirect coverage changes

[github-actions]

Commit: 1fedf6d

SP1 Performance Test Results

program	cycles	success
BTC_BLOCKSPACE	30,370,596	✅
EL_BLOCK	97,975	✅
CL_BLOCK	89,783	✅
L1_BATCH	30,419,814	✅
L2_BATCH	3,566	✅
CHECKPOINT	25,699	✅

[delbonis]

Nits, looks fine otherwise.

But why were all those lockfiles deleted?