Schematics testing infrastructure: ability to easily bootstrap a Tree

### Bug Report or Feature Request (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [x] feature request
```

### Desired functionality

I'd like to be able to more easily unit test individual Rules. and to do this, I'd like to be able to easily create a Tree on the fly.

My current strategy is to create a new schematic for the sole purpose of testing. But there is quite a bit of boilerplate that goes into this: the schematic code, the schema, the build rules, the awkward dependency of the test on this schematic, and the construction of a new schematicRunner in the test. Furthermore, different Rules need different Tree "boilerplate" for testing, so instead of creating a new schematic for each, I've just been jamming all the different types of files I need into this one test-only schematic, which is becoming unwieldy - which files are for testing which Rules?

Sometimes, I am testing a really simple Rule that only operates on one file, and I just want to be able to ask some function: "give me a tree with one file at this certain path with this certain content" or "give me a tree with an empty file at this path" and so on.

I think it'd be great if there was some testing infrastructure that could cook up a quick Tree in place. Or - does something like this already exist?

首先阅读现有的仅用于测试的 Schematic 设置，包括其 Schematic 代码、schema、构建规则以及测试中 SchematicRunner 的构造。比较各个 Rules 使用的不同 Tree 样板，并定义一个能够创建所请求文件和内容的小型测试入口点；当 Rules 无需专用 Schematic 即可进行单元测试时，即表示完成。

由索引模型根据 Issue 内容生成。