Allow specifying different column facets per table in TPT, TPC or entity splitting

[AndriySvyryd]

Split off from #19811

modelBuilder.Entity<Customer>().ToTable("Customer");
modelBuilder.Entity<SpecialCustomer>().ToTable("SpecialCustomer", tb =>
{
    tb.Property(c => c.Id)
        .HasDefaultValue("1")
        .HasDefaultConstrainName("blah")
        .HasDefaultValueSql("newid()")
        .HasComputedColumnSql("1")
        .HasConversion<string>()
        .HasColumnType("nvarchar(100)")
        .IsRequired(false)
        .HasMaxLength(100)
        .IsUnicode(false)
        .HasPrecision(1, 2)
        .HasCollation("Latin1_General_BIN2");
});

[maximcus]

@AndriySvyryd @ajcvickers I'm interested in #24685. Is this planned for EF Core 8 release by any chance?

[AndriySvyryd]

@maximcus No. Vote (👍) for both issues so we consider them for future releases

[maumar]

This is also a problem for explicit constraint names (e.g. key constraint, default constraint)

[kescherCode]

This issue is making itself quite apparent when you want to set a database computed column on a TPC entity, but not others of the same inherited type.