Adding config step to output the bisect config dictionary.

scripts/slave/recipes/bisect.expected/encoded_config_test.json

 [
   {
     "cmd": [
       "python",
       "-u",
       "[BUILD]/scripts/slave/bot_update.py",
       "--master",
       "tryserver.chromium.perf",
       "--builder",
       "linux_perf_bisect_builder",
@@ skipping 56 matching lines @@
       "[DEPOT_TOOLS]/gclient.py",
       "runhooks"
     ],
     "env": {
       "GYP_DEFINES": "branding=Chrome buildtype=Official component=static_library gomadir='[BUILD]/goma' target_arch=x64 use_goma=1"
     },
     "name": "gclient runhooks"
   },
   {
     "cmd": [
+      "echo",
+      "{\n  \"bad_revision\": \"src@a6298e4afedbf2cd461755ea6f45b0ad64222222\", \n  \"bug_id\": \"425582\", \n  \"builder_host\": \"master4.golo.chromium.org\", \n  \"builder_port\": \"8341\", \n  \"command\": \"tools/perf/run_benchmark -v --browser=release page_cycler.intl_ar_fa_he\", \n  \"dummy_builds\": true, \n  \"dummy_regression_confidence\": \"95\", \n  \"good_revision\": \"306475\", \n  \"gs_bucket\": \"chrome-perf\", \n  \"max_time_minutes\": \"5\", \n  \"metric\": \"warm_times/page_load_time\", \n  \"poll_sleep\": 0, \n  \"repeat_count\": \"2\", \n  \"test_type\": \"perf\", \n  \"truncate_percent\": \"25\"\n}"
+    ],
+    "name": "config"
+  },
+  {
+    "cmd": [
       "git",
       "footers",
       "--position",
       "a6298e4afedbf2cd461755ea6f45b0ad64222222"
     ],
     "cwd": "[SLAVE_BUILD]/src",
     "name": "resolving hash a6298e4afedbf2cd461755ea6f45b0ad64222222",
     "stdout": "/path/to/tmp/"
   },
   {
@@ skipping 996 matching lines @@
     "stdout": "/path/to/tmp/"
   },
   {
     "cmd": [
       "cat"
     ],
     "name": "Results",
     "stdin": "\n===== BISECT JOB RESULTS =====\nStatus: Successful\n\nTest Command: tools/perf/run_benchmark -v --browser=release page_cycler.intl_ar_fa_he\nTest Metric: warm_times/page_load_time\nRelative Change: 75.00%\nEstimated Confidence: 99.90%\nRetested CL with revert: Not Implemented.\n===== SUSPECTED CL(s) =====\nSubject : Some random CL\nAuthor  : DummyAuthor, dummy@nowhere.com\nCommit description:\n  A long description for a CL.\nContaining multiple lines\nCommit  : 00316c9ddfb9d7b4e1ed2fff9fe6d964d2111111\nDate    : 01/01/2015\n\ncommit_pos revision_string                              mean_value std_err good_or_bad? tested? culprit? \n306475     306475                                       80         10      good         tested  False    \n306476     306476                                       70         2       good         tested  False    \n306477     306477                                       15         1       bad          tested  True     \n306478     src@a6298e4afedbf2cd461755ea6f45b0ad64222222 20         1       bad          tested  False    \n\n==== INSTRUCTIONS TO REPRODUCE ====\nTo run locally:\n - Use the test command given under 'BISECT JOB RESULTS' above.\n - Consider using a profiler. Pass --profiler=list to list available profilers.\n\nTo reproduce on a performance try bot:\ntools/perf/run_benchmark -v --browser=<bot-name> page_cycler.intl_ar_fa_he\n(Where <bot-name> comes from tools/perf/run_benchmark --browser=list)\n\nFor more details please visit\nhttps://sites.google.com/a/chromium.org/dev/developers/performance-try-bots\n\n| O O | Visit http://www.chromium.org/developers/core-principles for Chrome's\n|  X  | policy on perf regressions. Contact chrome-perf-dashboard-team with any\n| / \\ | questions or suggestions about bisecting. THANK YOU."
   }
 ]