refactor: move mock data into arch_overlay

[dhower-qc]

This also required some restructuring around Ruby portfolios, since we
have to start with ConfiguredArchitecture to pull in overlays.

[dhower-qc]

@henrikg-qc

[james-ball-qualcomm]

There are some fundamental changes you've made here that I'm not clear why/what is happening now. If you want me to help maintain this code going forward, can you please setup a meeting with me to go over your changes together?

[james-ball-qualcomm]

Okay, I've thought about this some more and realize this isn't what I want at all. Instead of moving the mock things into an overlay, I want a mock arch directory and then move the mock things into that. Then have the tools that operate on the arch directory be able to point to the real arch directory or the mock arch directory. I know you've hard-coded the path to the architecture directory in many places so those would have to be changed to accept some-kind of global variable containing the path to use (say either "arch" or "mock_arch"). We'll need the mock arch directory in order to make unit-level regression tests that examine the generated output (e.g., adoc files) to determine pass/fail.

[dhower-qc]

Why is that better than this solution? Either way, you can use the tools to inspect only Mock data.