Package should not allow deployment with dev baby-yoda.yaml by default

The baby-yoda.yaml is critical to the functionality of the plugin, but currently can be deployed with a developer default that poses a risk to production environments. It should

• Require a baby-yoda.yaml be added by default
• Allow a file to be parsed vs inlining yaml since these will be very large and edited by multiple parties in production
• Clearly state in the README this as a required step and how to create/utilize for a deployment of this package