Static view registrations with package root asset specifications

I'm not entirely sure this isn't the intended behavior, but I ran into this and couldn't find anyone discussing exactly this in a previous PR or issue.

Rather than bother you all with whether or not to fix/change this, I thought it was a good opportunity to dig in and just see how some of the internals work to try to fix it.

Here's a PR with a failing test in one commit and then a subsequent commit that fixes it and adds a CHANGES comment.

Let me know if I'm mistaken and this is inappropriate or something needs re-working / re-wording since it's my first time contributing to Pyramid and I may have missed some aspect of process / policy.

Thanks!