Feature/1092 twig namespaces

[zhawkins]

Currently we're finding the twig partial folder by splitting the path based on the namespace ID (i.e. Atoms). This works well if we're using the atomic naming convention but not so much for others. At work we use Drupal theme names as our twig namespaces so this breaks in new and wondrous ways for us.

This PR updates how the fullFolderPath is generated. Instead of splitting on namespace ID we're splitting on the resolved namespace path. This allows us to leave the ID out of it while still figuring our the correct partial folder.

Before:

tempPartial = '/Users/foo/Sites/pattern-lab/source/_patterns/05-test/00-test.twig'

selectedNamespace[0].id = 'some_thing'

const fullFolderPath = `${
  tempPartial.split(selectedNamespace[0].id)[0]
}${selectedNamespace[0].id}`;

fullFolderPath = '/Users/foo/Sites/pattern-lab/source/_patterns/05-test/00-test.twigsome_thing'

After:

tempPartial = '/Users/foo/Sites/pattern-lab/source/_patterns/05-test/00-test.twig'

selectedNamespace[0].paths[index] = 'source/_patterns/05-test'

const fullFolderPath = `${
  tempPartial.split(selectedNamespace[0].paths[index])[0]
}${selectedNamespace[0].paths[index]}`;

fullFolderPath = '/Users/foo/Sites/pattern-lab/source/_patterns/05-test'

Closes #1092

[zhawkins]

@sghoweri , I believe you worked on this code at some point so maybe you can help me figure out if there's a better way to do this. 👋

[mariohernandez]

Tested patch locally and confirmed issues with warnings during npm run build about not finding the corresponding patterns, have been fixed.

[bmuenzenmeyer]

thank you @zhawkins and @mariohernandez for the fix and verification - it goes a long way toward helping make PL the cross-platform / cross-language thing we rely on