Write keys to parent app data dir if available

[marcguyer]

• Addresses Script to generate keys writes to vendor dir #35
• Create a data/oauth subdir for organization
• Added error handling for, among other things, openssl ext availability
• Convert to "bin" per "bin" or "scripts" for bin/generate-keys.php? #3 so parent app can run composer zend-expressive-authentication-oauth2-generate-keys

[ezimuel]

@marcguyer thanks for this PR. Everything looks good to me. I've only one concern about the name of the script bin/zend-expressive-authentication-oauth2-generate-keys, it looks verbose. Why we cannot use a short name like bin/generate-oauth2-keys?

[marcguyer]

I had a similar thought but decided to start with "most verbose" and see what you thought. I think it's best to use a convention of <package id prefix>-<script purpose> but I agree that the full package name as a prefix is probably overboard. How about ze-oauth2-generate-keys?

[ezimuel]

I think the most important point here is simplicity and usability. We can just use a name that reflects the action provided by the script. I would prefer generate-oauth2-keys. People can use this script also for oauth2.thephpleague.com. What do you think?

[marcguyer]

Ok, I think we're all set.

[ezimuel]

@marcguyer thanks!