Disallow HasMany setters

[zeitlerc]

HasMany properties are created as session-managed collections. Setting those managed collections to unmanaged collections can cause mysterious bugs or other issues. Argo should automatically initialize the HasMany collection and remove/prevent a setter on that property. This would force consumers to use the appropriate Add/Remove/Clear methods, which would prevent certain bugs at compile time.

[zeitlerc]

Using initialization setters causes a bug

public class Person
{
    // Collection is set even though setter method is disallowed by weaver, and IDs never return
    [HasManyIds("addresses")]
    public IEnumerable<Guid> AddressIds { get; } = new List<Guid>();

    [HasMany]
    public IEnumerable<Address> Addresses { get; set; } = new List<Address>();
}