Faker release policy and cadence

[damienwebdev]

After a discussion with @Shinigami92 I think it makes sense to outline a release policy for Faker. We are planning on following semver, but we have yet to explicitly state the following for library consumer guarantees:

Stability and Reliability

1. We plan on releasing "x" versions per "y" time period (release cadence)
2. We plan on dropping support for deprecated APIs every "z" releases (backwards compatability)

I would like to be honest with our consumers about what to expect in terms of deliverability, i.e. if we're likely not to deliver a release every "x" period, we just state that very clearly ala something like: "We're a small team, but we all have day jobs, releases will come as we have availability".

I'd like to open this discussion to outline and gather feedback on these topics.