feat(core): allow dev_path, dist_dir as array of paths, fixes #1897

[lucasfernog]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• New Binding Issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes. Issue #___
• No

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[lucasfernog]

The downside of this is that public paths get messy when specifying a file path on the array (currently I just assume it's a root file path). Ideally users should put all their front end assets on a specific folder and point devPath/distDir to that folder, but I agree it's easier to use an array when the frontend is very simple (like most of our examples).