no-process-env: accept a custom error message

I have created a wrapper around process.env, and would like to enforce developers use the wrapper instead of directly using `process.env`.

All this rule needs is to be able to accept a custom error message in the eslint config. Any thoughts, objections, opinions?