update prompts to think about order of tasks and steps

pilot/prompts/components/execution_order.prompt

@@ -0,0 +1 @@
+All the steps will be executed in order in which you give them, so it is very important that you think about all steps before you start listing them. For example, you should never code something before you install dependencies or you should never try access a file before it exists in project.

pilot/prompts/dev_ops/debug.prompt

@@ -17,6 +17,8 @@ Each step can be either:
 * `code_change` -  step will change the code and you need to thoroughly describe what needs to be implemented. I will implement the requested changes and let you know.
 * `human_intervention` - if you need the human to do something, use this type of step and explain in details what you want the human to do.
 
+{{ execution_order }}
+
 Also, make sure that at least the last step has `check_if_fixed` set to TRUE.
 
 {{ file_size_limit }}

pilot/prompts/development/iteration.prompt

@@ -44,6 +44,8 @@ Tell me all the new code that needs to be written or modified to implement curre
 **IMPORTANT**
 When there is an error in the code, the best way to debug the issue is to understand the values of different variables so usually, developers put logs around the code and print out the values variables important to fix this issue. If, and only if, your colleague's report is a bug report and not an improvement request, think about variables that you would like to know the value of in the code that would help you fix this issue and then add logs around the code that will help you resolve this issue. Whenever you add a log that is meant to debug an issue, on the each line on which you add a log, you **MUST** append a code comment `gpt_pilot_debugging_log` (for example, `// gpt_pilot_debugging_log` or `# gpt_pilot_debugging_log`) so that the developer can remove all these logs after this issue is fixed.
 
+{{ execution_order }}
+
 {{ file_size_limit }}
 
 You do not need to make any automated tests work.

pilot/prompts/development/parse_task.prompt

@@ -9,6 +9,8 @@ Each step can be either:
 
 If the step is of type `save_file` or `modify_file`, it needs to contain instructions on how to change only ONE file.
 
+{{ execution_order }}
+
 {{ logs_and_error_handling }}
 
 **IMPORTANT**: In `code_change_description` field of `modify_file` step, you must provide full information (including code samples, if any) from the previous message, so that the developer can correctly implement the change.  For `save_file`, you MUST include FULL file contents, without omitting anything or adding comments like `// rest of the code goes here`.

pilot/prompts/development/task/breakdown.prompt

@@ -28,6 +28,8 @@ You do not need to make any automated tests work.
 {% endif %}
 DO NOT specify commands to create any folders or files, they will be created automatically - just specify the relative path to each file that needs to be written.
 
+{{ execution_order }}
+
 {{ human_intervention_explanation }}
 
 {{ file_size_limit }}

pilot/prompts/development/task/update_task.prompt

@@ -33,6 +33,8 @@ code_change_description: `{{ step.code_change_description }}`{% endif %}
 {% endif %}
 Now, think step by step and create a new list of task steps to complete this task based on the output we got from running `{{ current_step.command.command }}`. It will either be the same as it is now or any of the Next Task Steps may or may not be needed anymore.
 
+{{ execution_order }}
+
 {{ file_size_limit }}
 
 {#