Remove task-specific schema from hook.task

[kritisingh1]

This is in reference to Bug 1438019 which requires updating the current schemas in accordance with JSON-e so that hook.task has type: object.

[djmitche]

I'll post a longer comment about this issue in the bug, but for the moment, a quick note about commits and pull requests. A pull request and commit message should describe what is changing directly, rather than just referring to a bug. The title of this PR, "fixes Bug 1438019", doesn't tell me much (I don't remember what that bug number refers to!).

We have some guidelines in our documentation. Those are pretty common to git-based open source projects, not just Taskcluster, so a good skill to learn.

[djmitche]

This looks great!

Two things to add:

• a test that calls createTask with some nonsense in the task property, just to check
• title and description attributes in the schemas for the task indicating that the task property is a task template, which will be rendered with JSON-e as described in https://docs.taskcluster.net/reference/core/taskcluster-hooks/docs/firing-hooks

[djmitche]

I added a little bit more text to the description :)

[kritisingh1]

@djmitche the test that calls createTask still needs to be added, right? Thanks :)

[djmitche]

Oh right! Please make a new PR for that. Silly me!!

[kritisingh1]

Sure. Thanks a lot!