Adds support for username to match the v2 spec

The v2.0 API spec uses username for the user's name, whereas the v3 API
just uses name. The v2.0 implementaion incorrectly used name instead of
username, but did allow a username to be specified and stored in the
extras.

This patch makes the implementation more closely conform to the API
without breaking backward compatibility. Anyone using name in the v2.0
API can continue to do so. They can even specify a username that will
still get stored in the extras. Users can now use the documented
username instead of name and the API will work for them as well.

Both name and username will always be returned for the v2 API calls.

DocImpact
Change-Id: Ia95aa5d442a8311925399fa59e5022d31f68d374
Closes-Bug: #1214686
description is wrong in endpoint filter rst doc

Literal block must start and end with blank line.

Change-Id: Ib80bc76101da34b8251d731cee5b60bde45ec099
Closes-Bug: #1269300
append extension name to trust notifications

Change-Id: If1111dd39d9ad421fb7a6f23c9e2db4947387592
Merge "description is wrong in endpoint filter rst doc"
Merge "append extension name to trust notifications"
Merge "Adds support for username to match the v2 spec"