Remove duplication / improve organization on "context" properties

[mhoeger]

Originally posted here: Azure/azure-functions-host#4335
In the above issue, it was expected that context.bindings should include output binding names as well as input/trigger binding data. Although we could add output binding names to context.bindings, this issue is to track improvements around the organization and duplication of input and output binding data.

This issue tracks future breaking changes to the context object's properties

@JamieMagee as FYI. If you could also let us know what your expectations around output bindings were, and what confused you the most, it would be helpful!

[JamieMagee]

Thanks for following up with this. This doesn't necessarily need to be a breaking change right now. Updating the documentation you linked to change:

Returns a named object that contains all your input and output data

to

Returns a named object that contains all your input and trigger data

Would have saved me some time 😄

[mhoeger]

@JamieMagee - omg... haha thanks, fixing now :)

[mhoeger]

Much duplication was removed on the data passing layer but not on the "context" object itself - worth considering for V4, but for V3 we tended towards limiting breaking changes.

[ejizba]

This is likely something we can address in #480