unify turn annotation tasks (model chat and turn annotations static tasks)

[meganung]

Patch description

• makes the schema of JSON files for defining the annotation buckets the same between model chat task and turn annotations static task
  • flag name: annotations_config_path
  • schema example
• removes the unused task_description flag in model chat task
• chat_title → title_task in model chat task
• make task description a html file in turn annotations static task to match model chat task

Testing steps
Circle CI

[EricMichaelSmith]

Yeah these improvements are super super useful to have, thanks a lot! Some comments about loose ends

[jxmsML]

@EricMichaelSmith @meganung I wonder if this logic work for non-checkbox inputtype, e.g. "radio" button,

suppose you click radio_bucket1, and then changed it to radio_bucket2,
I guess in this case, both radio_bucket1, and radio_bucket2 are True, which is not exatly what we want

[jxmsML]

shall we remove L31? and always set inputType = checkbox

[meganung]

it does work if you specify type: radio in the config - i've done it in turn annotations static tasks at least. Radio buttons you can only select one so only one will be True.

[EricMichaelSmith]

Hmm interesting - @meganung in that case, do you expect that radio boxes will work correctly in the current version of model_chat as well, given this PR? I suppose I see two possibilities:
(1) we test out that radio buttons render correctly in the current version of model chat (i.e. with only one being checked at once as @jxmsML notes) and then add documentation about how to enable that to the README. In this case we should also add a unit test for radio buttons (or a TODO for a unit test at the very least, although a unit test is of course better)
(2) we just fix input_type = checkbox for now, as @jxmsML suggests, and maybe add a TODO to add and test out radio box support for this task in the future

Either possibility is fine with me, but @meganung lemme know what you think :)

[meganung]

good catch @jxmsML and thanks for the input @EricMichaelSmith -- I manually tested it and the frontend is fine (visually you can only check one) but our code for updating the data doesn't do that so ends up saving multiple different values as true if the user switches between selecting different radio buttons. I added a TODO for now since adding support for radio buttons in model chat task can be a separate PR.

[jxmsML]

cool look good! @EricMichaelSmith just wonder if these frontend changes (e.g. checkbox type) that might affect final data logged has a test somewhere in crowdsourcing task (or will be catched?)

[EricMichaelSmith]

@jxmsML Hmm, anything that affects the final data will break one of the tests, yes - I see that Megan fixed the tests in this PR, but it doesn't look like she needed to fix anything related to the checkbox type, so presumably the checkbox type doesn't get saved in the final data :)

[jxmsML]

LGTM!! awesome job @meganung

[EricMichaelSmith]

Yeah thanks a lot @meganung , this is super useful!