Apply attributes recursively for nested classes

[mvdfugro]

This resolves #3888 by applying all attributes recursively for nested classes.

Although this is a nice solution in terms of consistency, it also has a somewhat higher risk of breaking backwards compatibility (in all test cases in the world there is probably someone depending on the non-inheritance of attributes). So maybe this is an OK solution for 4.0+ but not for backporting to 3.x. An interesting example of this is the Ignore attribute:

    [TestFixture]
    [Ignore("testing ignore a fixture")]
    public class FixtureUsingIgnoreAttribute
    {
        [Test]
        public void Success()
        {
        }

        public class SubFixture
        {
            [Test]
            public void Success()
            {
                // this is currently a test that runs, but gets ignored with this change
            }
        }
    }

A safer (but less consistent) solution would filter the recursive application for specific attributes (maybe based on an explicit interface?)

Note that branch is 'on top of' #3843 as it depends (somewhat) on the new test system added there. The framework changes should apply to master without any changes.

[rprouse]

It looks like this has the changes from your other PR mixed up in it. I am going to hold off reviewing until that is merged.

[mvdfugro]

Indeed this is based on the other PR (as otherwise I had no failing tests to fix ;-)). I'll rebase this on master once the other request is merged back there.

[mvdfugro]

Rebased on latest master. Now the review only contains the three relevant commits :-)

Fundamentally, two changes have been made:

• Attributes are now applied recursively (and I've also added a test for the Ignore attribute),
• HasLifeCycle has been simplified to just use the first TestFixture found. I believe this is what the actual behavior already was (as there only is a single TestFixture in the ITest.Parent hierarchy) but this more clearly communicates that this is not where the inheritance happens. See the discussion on FixtureLifeCycle not applied correctly to nested test classes #3888

[rprouse]