Legal warning on continuous run

[ntindle]

Background

We should warn users of the legal implications of using this autonomously.

Changes

Adds a legal blurb and utility for it

Documentation

Self documenting?

Test Plan

PR Quality Checklist

• My pull request is atomic and focuses on a single change.
• I have thoroughly tested my changes with multiple different prompts.
• I have considered potential risks and mitigations for my changes.
• I have documented my changes clearly and comprehensively.
• I have not snuck in any "extra" small tweaks changes

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 1 hour (more than 100, code: "api-deployments-free-per-day").

[codecov]

Codecov Report

Patch coverage: 16.66% and project coverage change: -0.09 ⚠️

Comparison is base (85fe6f3) 62.26% compared to head (1f487b3) 62.18%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4239      +/-   ##
==========================================
- Coverage   62.26%   62.18%   -0.09%     
==========================================
  Files          73       73              
  Lines        3339     3345       +6     
  Branches      482      484       +2     
==========================================
+ Hits         2079     2080       +1     
- Misses       1113     1118       +5     
  Partials      147      147              

Impacted Files	Coverage Δ
autogpt/main.py	0.00% <0.00%> (ø)
autogpt/utils.py	63.15% <33.33%> (-0.98%)	⬇️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 50 minutes (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 48 minutes (more than 100, code: "api-deployments-free-per-day").

[Boostrix]

I would suggest putting the text into a file and load it, that way this can be updated and reviewed in the future without requiring a code review?
Also, let's make it go through clean_input to confirm y/n ?