Move settings bundle to correct location (even in fallback cases)

[bitcrumb]

#195 moved the Resources group down into the project_namegroup. Code has been adapted to take this into account when moving the Settings.bundlearound.

Also fixed an issue where the file would be generated in the wrong location of one of the fallback parent_groups would be used.

[gfontenot]

Looking at this now, the amount of code needed for this fix is disconcerting. I'm wondering if we shouldn't re-think how this works so that we can simply specify this location in the template yaml.

[bitcrumb]

You're absolutely right, I'm not too happy about this code either, but it does fix it for now. Let me ponder on it some more. I like your suggestion that it should be configurable, that should make things more concise.

[gfontenot]

@bitcrumb Any new thoughts here?

[bitcrumb]

I guess specifying the location would be the simplest solution, with the main_group as a fallback. But I must admit that I lost track of this pull request. Will try to follow up on this in the coming days!

[gfontenot]

Does this PR fix the current problem of this being broken? If so, maybe we just push forward with this and create an issue to simplify this in the future.

[bitcrumb]

Yes it does. I'll let it up to you decide.

[gfontenot]

👍 I've rebased and merged this as fda83f4

I'll create an issue to track simplifying this.