Using protoc cli parameter to specify additional class derivations

[tim2CF]

The main feature of this PR is support of additional class instances for all generated types. Parameters for additional class deriving could be passed through protoc command-line argument. Example which enables stock deriving of GHC.Generics.Generic class for all generated haskell types:

--haskell_opt='Opt{ imports = [], pragmas = ["DeriveGeneric"], stockInstances = ["GHC.Generics.Generic"], defaultInstances = [] }'

• Introduce Data.ProtoLens.Compiler.Parameter module which enables usage of cli parameter from plugin.proto.
• Using Data.ProtoLens.Compiler.Parameter to enable additional stock deriving (useful for classes like GHC.Generics.Generic).
• Using Data.ProtoLens.Compiler.Parameter to enable additional default instances implementations (useful for classes which do support default implementations through GHC.Generics.Generic).

[google-cla[bot]]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[tim2CF]

This is quite small pull request, maybe I could receive some human feedback before google-cla bot approval. If changes could be merged in principle (maybe after some improvements) - then I'll sign cla. Otherwise it does not make much sense.

[blackgnezdo]

Thanks for the PR. It looks like a useful capability. I pointed out some areas for improvement. In addition to those, please add a test covering this newly added functionality.