Update suggestion on destroying VTU wrapper

What does this MR do?

The docs were suggesting a practice to avoid inconvenient situations generated from the way VTU is destroying a wrapper. Starting from VTU v1.x, the scenarios are mitigated from the library itself: trying operations on a destroyed wapper will display a warn.

Given we're now on VTU v1.1.2, this MR updates the docs suggestions to reflect this case.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• [-] Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team