[SIL][MoveOnlyChecker] Omit creation of destroy_addr instruction for UncheckedTakeEnumDataAddrInst preventing use after destroy for ~Copyable structs in special cases

[Rajveer100]

Resolves #80261

When assigning properties for non-copyable structs globally or in final class, a destroy instruction is incorrectly placed in the basic block causing compiler crash.

[Rajveer100]

Let me know if this isn't the right place to handle. Both cases provided by @YOCKOW do not crash after this change:

1:

struct NonCopyable: ~Copyable {
  var value: Int = 0
}

var nc: NonCopyable? = NonCopyable()
nc?.value = 1

2:

struct NonCopyable: ~Copyable {
  var value: Int = 0
}

final class Holder { // The compiler doesn't crash if this is a noncopyable struct.
  var nc: NonCopyable? = NonCopyable()

  func f() {
    nc?.value = 1
  }
}

[Rajveer100]

Sharing my thought process, referring from #80261 (comment):

I think that the problem is for optionals, when we are in a potentially global context (or final class), and there isn't any outer basic block, a consume is assumed by the checker causing destroy instruction to be inserted way early.

In this case, we are consuming before assigning the property for the non-copyable struct.