Add tempest test for template declaration

[Jeff Peeler]

This test will extend the existing template validation to include testing for all supported sections of a template:

AWSTemplateFormatVersion - just a version date
Description - valid JSON string
Parameters - supported properties: Type, Default, NoEcho, AllowedValues, AllowedPattern, MaxLength, MinLength, MaxValue, MinValue, Description, ContraintDescription
Mappings - name-value pairs that are accessed via Fn::FindInMap
Resources - composed of type (specified below) and optionally properties made up of string, list, dict, or result of function or reference - resources also output attributes which define the resource after it has been orchestrated
Outputs - output is composed of a double-quoted key name, a single colon, and one or more properties made up of value and an optional description

[Jeff Peeler (jpeeler-z)]

Review in progress: https://review.openstack.org/#/c/69726/

[Mike Spreitzer (mike-spreitzer)]

I decided to test the claim that the flavors used in the test do not need to exist. I edited the TemplateJSONTestFull class and replaced every occurrence of "m1.small" with "m1.xyzzy". Then I ran `testr run orchestration`. I got 3 failures, including two tracebacks showing the root problem was "ValueError: must be a valid EC2 instance type". Typescript attached.

[Mike Spreitzer (mike-spreitzer)]

Attached the modified test source.

[Mike Spreitzer (mike-spreitzer)]

Never mind comment 2 and comment 3, I overlooked the subclassing. When I replace *all* occurrences of "m1.small" with "m1.xyzzy" then the tests all succeed. So I think Jeff is right, no instances are being created.

[Angus Salkeld (asalkeld)]

tests are in-tree now.