Add support for new resourcesCFCPath setting

[dswitzer]

Added new resourcesCFCPath setting which allows you to configure the "resources" components path in cases where the "resource" folder may conflict with existing directory structures. The default behavior is unchanged (for backwards compatibility), you would only need to set this when the /resources folder conflicts with your existing application or you just want to use your own directory structure.

For example, instead of using the resources convention you could place your resources in a completely different directory using:

variables.framework.resourcesCFCPath = "private.api.components"

This would expect all your Taffy "resources" would live in the physical folder of expandPath('/private/api/components') and that your components can be creating using the dotted path prefix of private.api.components.

[netlify]

✅ Deploy Preview for taffy-docs ready!

Name	Link
🔨 Latest commit	ded9050
🔍 Latest deploy log	https://app.netlify.com/projects/taffy-docs/deploys/68b1c8a8bfa44b00085ab869
😎 Deploy Preview	https://deploy-preview-452--taffy-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

This pull request does not contain a valid label. Please add one of the following labels: ['Semver-Major', 'Semver-Minor', 'Semver-Patch']