fix(profile): use affiliation=own to get user repos

[blakegong]

Problem

The number of repositories on your own profile page is the same as shown on github.com, which is
(user.public_repos + user.total_private_repos). However, when the button is clicked, the repository list actually shows all the repositories where you have admin permission. The delta here as I observed, is the repositories in a private organization you are part of where you are also granted admin permission to.

Another minor issue is the current way of querying extra data then filter in client is inefficient compared to querying the exact data that the client actually wants:

git-point/src/user/user.action.js

Lines 132 to 136 in 809a809

	fetchUrl(`${url}/repos?per_page=50`, accessToken)
	.then(data => {
	const payload = isAuthUser
	? data.filter(repo => repo.permissions.admin)
	: data;

Approach

This PR uses affiliation=own from https://developer.github.com/v3/repos/#parameters to get user repos, which provides the exact data needed here. The number of repositories returned in this PR matches the number on user's profile page, which is (user.public_repos + user.total_private_repos).

[housseindjirdeh]

I had no idea there was an affiliation filter we could use! Thanks @blakegong, agreed it makes much more sense to leverage this than to do our workaround 😅

Thanks again <3

[housseindjirdeh]

🎉

[blakegong]

Wow this is fast! Thanks 😄