Performance: Consider a different schema for provider urls

tweaked this to be less spread out, reduced it to one file per quarter.

Im still not sure this is better, however. Ultimately, composer has to download all of the provider include files the first time, so it only reduces the number of http requests, but not the amount of data needed to be downloaded.

As time passes, however, I believe that we're actually increasing the likelyhood of composer needing to download more data, rather than less, as each change will affect a larger provider file now.

Either way, however, this change is trivial and we can tune it to what ends up working best, in reality.

This is fixed, and is now doing a %4 on the month. Which I now realize is not exactly what I want. (1,5,9/2,6,10/3,7,11/4,8,12 are not great ways to split up chronological files.

Okay, this got in. we'll see if this is a fair number of includes or not.