GA is available on GitHub pages, there's an input for the ID in the settings. GitHub doesn't use GA, so there's also no need to implement two trackers, having an input for a GA ID in the repository settings would be enough.
Personally, I don't think Analytics is a good measurement of a project on GitHub, I would be more inclined to look at the number of clones, forks, downloads from the releases page, pull requests, and the number of commits being made.
GitHub made better repo analytics available yesterday, and is basically exactly what you described: https://github.com/blog/1672-introducing-github-traffic-anal...
GA allows to use two trackers, so any page could be set up with their ID and the project's owner's.