Add SurfaceProducer.onSurfaceCleanup, deprecate onSurfaceDestroyed. - #160937

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…61252)

Follow-up to #160937
(#160933).

This more or less mirrors what we did already for `onSurfaceCreated` to
match `onSurfaceAvailable`.

With this approach, the master branch should immediately start seeing
better behavior in terms of being able to use the `onSurfaceDestroyed`
callback effectively (before the surface has been released). For
example, for a plugin that already uses `onSurfaceDestroyed`, [i.e
`camerax`](https://github.com/flutter/packages/blob/97ce56a68eea650dc784617b4eed7814cccedeb8/packages/camera/camera_android_camerax/android/src/main/java/io/flutter/plugins/camerax/PreviewHostApiImpl.java):

```java
@OverRide
public void onSurfaceDestroyed() {
  // Invalidate the SurfaceRequest so that CameraX knows to to make a new request
  // for a surface.
  request.invalidate();
}
```

... the request is now invalidated _before_ the surface has been
destroyed, which is what (I believe) we wanted?

---

Folks that want to publish package updates that _definitely_ use the
correct timing will have to wait for the next stable.

/cc @hasali19 would be great to get your input here.

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…utter#161252)

Follow-up to flutter#160937
(flutter#160933).

This more or less mirrors what we did already for `onSurfaceCreated` to
match `onSurfaceAvailable`.

With this approach, the master branch should immediately start seeing
better behavior in terms of being able to use the `onSurfaceDestroyed`
callback effectively (before the surface has been released). For
example, for a plugin that already uses `onSurfaceDestroyed`, [i.e
`camerax`](https://github.com/flutter/packages/blob/97ce56a68eea650dc784617b4eed7814cccedeb8/packages/camera/camera_android_camerax/android/src/main/java/io/flutter/plugins/camerax/PreviewHostApiImpl.java):

```java
@OverRide
public void onSurfaceDestroyed() {
  // Invalidate the SurfaceRequest so that CameraX knows to to make a new request
  // for a surface.
  request.invalidate();
}
```

... the request is now invalidated _before_ the surface has been
destroyed, which is what (I believe) we wanted?

---

Folks that want to publish package updates that _definitely_ use the
correct timing will have to wait for the next stable.

/cc @hasali19 would be great to get your input here.

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)

…estroyed`. (flutter/flutter#160937)