[FIX] Allow resource migration

[flovogt]

Allow the usage of a non compliant resource object when writing

[coveralls]

Coverage decreased (-0.3%) to 86.971% when pulling f976574 on allow-resource-migration into 1060810 on next.

[matz3]

What was the scenario where this is relevant?

[flovogt]

We've adjusted the openui5-sample-app with a custom task and a custom middleware to see if its possible to run a v2 configured middleware in the v3 tooling.
The issue occurs when a custom task is importing a fs/Resource from their dependencies. So its a v2 resource. Now, this resource instance is given to any (e.g. workspace.write) API which we inject into the custom task call. This injected API is v3. With that the v3 API has to handle a v2 artefact.

• openui5-sample-app https://github.com/SAP/openui5-sample-app/tree/custom-middleware-task
• custom task using a v2 resource and using the injected UI5 Tooling API https://github.com/ui5-community/ui5-ecosystem-showcase/blob/main/packages/ui5-task-zipper/lib/zipper.js#L89

[RandomByte]

Related change in earlier v2 development: #270