environmentConfigs type enum

### What happened?
``` yaml
...
type: selector
...
```

I didn't know the type should be capitalized. I spent a chunk of time trying to chase down the issue I was experiencing.

Turns out I should have capitalized `Selector`. 🙃

No rush, but for usability, doing some kind of input validation on what should be a binary enum would prevent the troubleshooting rabbithole I went down for a single char diff.

### How can we reproduce it?
Be new to the function or just mistype the type of selector.

### What environment did it happen in?
Function version: v0.0.7