PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/NativeScript/blob/master/DevelopmentWorkflow.md#running-unit-tests.
• Tests for the changes are included - https://github.com/NativeScript/NativeScript/blob/master/WritingUnitTests.md.

What is the current behavior?

Views and view trees are destroyed when removed from the view tree.

What is the new behavior?

Views can be marked as reusable and will not be destroyed when removed from view tree. Removing these nodes require the developer to do:

view.destroyNode();
// which calls
view.reusable = false;
view._tearDownUI();

For implementation details on how frameworks should deal with it, see my work in nativescript-angular: https://github.com/edusperoni/nativescript-angular/tree/reusable-views

Implements #7469.

To be defined:

What happens when a reusable view with children gets removed? The current implementation does not call _tearDownUI on children, but we should still suspendNativeUpdates down the chain (this._suspendNativeUpdates(SuspendType.UISetup);).

Maybe we should we create a new SuspendType (Detached)? Maybe this isn't even needed as the view should be unloaded by _removeViewCore which eventually calls this._suspendNativeUpdates(SuspendType.Loaded); on all children.

Possible refactoring needed (not directly related to this PR)

The current logic of _resumeNativeUpdates will call initNativeView. In most places I checked, initNativeView creates delegates that are only removed in disposeNativeView. This behavior is probably already an issue on loading/unloading views (like navigation) because of this._resumeNativeUpdates(SuspendType.Loaded);, meaning initNativeView is called multiple times during the application lifecycle, but the delegates are only cleaned up once.

During my tests with WebView, calling initNativeView did not result in a performance impact