Add an (author only) AddonViewSet list function

[eviljeff]

Fixes mozilla/addons#16378

Description

Enables GET on /api/v5/addons/addon/ to list all the add-ons the user is an author of. Also implements ?sort= and ?type= to match functionality on existing devhub

Context

• name is omitted from a possible sort, after talking with Mat (perf concerns).
• all sort parameters default to ascending and can be made descending with a - prefix, e.g. ?sort=-created, which is different to the /addons/search/ endpoint, which only supports descending (i.e. sort=created is already descending, and can't be reversed to ascending). The sort options also match the detail field naming (e.g. average_daily_users rather than users)

Testing

It's a little annoying to test, because by definition you need auth

• To test without auth first, access http://olympia.test/api/v5/addons/addon/ - should be empty
• To test with auth, you need to send the header Authorization with the value Session xxxxx where xxxxx is your session id (you can get it from your cookie). You can use curl, some other tool, or devtools in Firefox with Edit & Resend.
• http://olympia.test/api/v5/addons/addon/ with the auth header should return the same list of add-ons as developer hub /developers/addons/ page
• http://olympia.test/api/v5/addons/addon/?type=extension should just show extensions, etc with all the valid addon types (can be a comma-separated list)
• http://olympia.test/api/v5/addons/addon/?sort=created should sort the list by created ascending, -created by created descending (can also be a comma-separated list, but it's less useful because all of the sort fields we offer now have numeric values)

Checklist

• Add #ISSUENUM at the top of your PR to an existing open issue in the mozilla/addons repository.
• Successfully verified the change locally.
• The change is covered by automated tests, or otherwise indicated why doing so is unnecessary/impossible.
• Add before and after screenshots (Only for changes that impact the UI).
• Add or update relevant docs reflecting the changes made.

[nothingrandom]

I would have some questions as an end user to some of these;

average_daily_users, hotness, and weekly_downloads I'd expect to look similar
bayesian_rating and ratings.bayesian_average -> is this the star rating for the addon?
last_updated -> does this go for the updated approved, or updated uploaded?

[eviljeff]

They match the fields in the detail section for consistency - do those fields need further explanation? And/or a sentence explaining the connection?

I'd expect to look similar

Not sure what you mean here - that the naming is self explanatory or you think they're obsolete?