Do not generate TextAlignment extension if it's already generated by base type

[Youssef1313]

Another suggested fix: #206

(ONLY ONE of the PRs need to be merged)

Description of Change

Linked Issues

• Fixes [BUG] TextAlignment Extension Throwing Compiler Error #182

PR Checklist

• Has a linked Issue, and the Issue has been approved(bug) or Championed (feature/proposal)
• Has tests (if omitted, state reason in description)
• Has samples (if omitted, state reason in description)
• Rebased on top of main at time of PR
• Changes adhere to coding standard
• Documentation created or updated: https://github.com/MicrosoftDocs/CommunityToolkit/pulls/XYZ

Additional information

[Youssef1313]

new Derived().M();

public class Base
{
}

public class Derived : Base
{
}

public static class Extensions1
{
    public static void M<T>(this T b) where T : Base { }
}

public static class Extensions2
{
    public static void M<T>(this T b) where T : Derived { }
}

@pictos Currently, we generate two generic extensions like these. The fact that they are generic is why the compiler actually complains.

If we generate it like this:

new Derived().M();

public class Base
{
}

public class Derived : Base
{
}

public static class Extensions1
{
    public static void M(this Base b) { }
}

public static class Extensions2
{
    public static void M(this Derived b) { }
}

It will compile just fine.

Is it possible that we switch to the non-generic approach?

[pictos]

@Youssef1313 here's some context around the usage of generics
#150

[Youssef1313]

Ok, I think we can go with this approach.

[brminnick]

Thanks @Youssef1313!!

Apologies for not merging this sooner 🙌