SQL Server UseIdentityColumn() (and others) are incompatible with value generation

[roji]

Try to call UseIdentityColumn() on a property that has a value converter configured fails with: "Identity value generation cannot be used for the property 'Id' on entity type 'Blog' because the property type is 'BlogId'. Identity value generation can only be used with signed integer properties."

Removing the explicit UseIdentityColumn() (but leaving ValueGeneratedOnAdd()) succeeds, creating an identity column as expected - it seems like our check for UseIdentityColumn() compatibility (and other similar value generation strategies) is too strict.

On a related note, leaving out ValueGeneratedOnAdd() doesn't create an identity column at all, although my expectation here is for that to happen, as the property is still called Id and has a provider type of int (but my expectation here may be wrong).

Originally opened by @grzegorzkarolewski against PostgreSQL in npgsql/efcore.pg#3141.

Repro

await using var ctx = new BlogContext();
await ctx.Database.EnsureDeletedAsync();
await ctx.Database.EnsureCreatedAsync();

public class BlogContext : DbContext
{
    public DbSet<Blog> Blogs { get; set; }

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        => optionsBuilder
            .UseSqlServer(@"Server=localhost;Database=test;User=SA;Password=Abcd5678;Connect Timeout=60;ConnectRetryCount=0;Trust Server Certificate=true")
            .LogTo(Console.WriteLine, LogLevel.Information)
            .EnableSensitiveDataLogging();

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        modelBuilder.Entity<Blog>()
            .Property(b => b.Id)
            .ValueGeneratedOnAdd()
            .UseIdentityColumn()
            .HasConversion(i => i.Value, v => new BlogId { Value = v });
    }
}

public class Blog
{
    public BlogId Id { get; set; }
    public string? Name { get; set; }
}

public class BlogId
{
    public int Value;
}

,/details>