Deprecate no-op assignments

[Herringway]

Who hasn't been bitten by this bug?

struct Foo {
  int bar;
  this(int bar) {
    bar = bar;
  }
}

Instead of assigning the constructor parameter to the struct member as intended, this does nothing. Oops.

As long as there's no opAssign overload involved, these mistakes are guaranteed to be no-ops. Let's make them errors instead.

[thewilsonator]

This is a duplicate of a bug I have reported in the past. Can't remember what number it is though.

[ntrel]

@thewilsonator #17874