Support different account linking parameters and lambda env vars for live and dev skills

[galah92]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request 
[ ] Other... Please describe: 

Expected Behavior

I'm setting up a Smart Home Alexa skill, along with my own backend and implementing account linking.
I've got two environments for my backend (dev & prod), including two authorization services, backend URLs, etc. Having my skill certified, I now have two versions of my skill - "Live" and "In Dev".

I'd like to configure it such that the "In Dev" skill instance will communicate with my dev environment. This means different Account Linking parameters currently configured in the web console (Web Authorization URI. Access Token URI, etc), and different environment variables to the lambda function (and if possible, a different lambda).

Moreover, I currently have a CI&CD pipeline capable of deploying code to my two environments. I'd like integrate Alexa skill deployment accordingly.

Is all this possible right now? If so, can you direct me to the documentation? It seems like the ASK CLI has no way to differentiate between the "Live" and "In Dev" skill instances.