Previously, when defining dependencies in a pod spec, an error would be thrown if
the parent spec's name includes the dependency name (because it thinks a cyclic
dependency is created). For example, a pod spec named 'SpecTest' would incorrectly
fail if one of it's sub specs had a dependency on a pod named 'Spec'.
Added an additional unit test to handle the case where a sub-sub-spec
is dependant upon a parent. Also added a unit test for the case where
a sub-spec is dependant on a pod whose name closely matches one of it's