Add AgentRejectAction across multiple modules

[li-boxuan]

This commit introduces the AgentRejectAction class and integrates it across various modules and actions. It includes updates to READMEs, action definitions, and agent controllers to handle the new 'reject' action. This functionality will allow agents to properly signal task rejection.

===========BELOW COMMIT MESSAGE IS GENERATED BY OPENDEVIN=============

Yes, again I am too lazy to write a commit message by myself. So I asked OpenDevin to do me the favour:

WORKSPACE_MOUNT_PATH="`PWD`" SANDBOX_TYPE="exec" poetry run python opendevin/core/main.py -t "write a commit message" -c ManagerAgent -d ./

Why this PR is needed?

1. To give the user and/or delegator agent a chance to rethink about the task
2. To encourage agent developers to think about edge/failure cases. E.g. without the prompt change included in this PR, CommitWriterAgent never finishes when running in a non-git folder
3. To differentiate between success and failure (ofc). Without this PR, we don't know if There is no diff in the staging area; no changes to commit. output from CommitWriterAgent really means there's no change to commit, OR the output itself is literally the compiled commit message.

TODO in this PR:

• Update backend_architecture.puml This should be a separate issue.

Future work:

• Add integration test for Reject
• Delegator should be able to rethink about the task assignment
• Micro-agents should have enforcements for their inputs & outputs schema
• UI changes to differentiate between "Finish" and "Reject"
• Any other agent needs to use "Reject" action?

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 81.81818% with 2 lines in your changes are missing coverage. Please review.

❗ No coverage uploaded for pull request base (main@242c4a0). Click here to learn what that means.

Files	Patch %	Lines
opendevin/controller/agent_controller.py	0.00%	1 Missing ⚠️
opendevin/events/action/agent.py	87.50%	1 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1615   +/-   ##
=======================================
  Coverage        ?   39.05%           
=======================================
  Files           ?       92           
  Lines           ?     3731           
  Branches        ?        0           
=======================================
  Hits            ?     1457           
  Misses          ?     2274           
  Partials        ?        0           

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

[rbren]

I don't think this should have an arbitrary dict of outputs, the way finish does. All we want is a reason

[li-boxuan]

I see where you are coming from, but I have a few counter-arguments:

1. An agent can choose to have more than just a reason attribute. For example, it can suggest how to fix the task in addition to a reason.
2. Both AgentRejectAction and AgentFinishAction are termination actions, so it's better for them to have the same interface IMO.
3. By design, a micro-agent has a schema for inputs and outputs. We don't really enforce it at the moment (i.e. a micro-agent can finish with whatever outputs type), but I feel like we should do it sooner or later. If AgentRejectAction and AgentFinishAction could have different schema for outputs, things will become trickier.

[li-boxuan]

Will create a follow-up to enforce the schema for micro-agents. We could discuss if we want to continue this approach there.

[rbren]

Very cool! Agree this will be useful