fix: support platform specific files that are not directly imported anywhere in the app

[DimitarTachev]

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-dev-webpack/blob/master/CONTRIBUTING.md#testing-locally-by-running-e2e-tests
• Tests for the changes are included.

What is the current behavior?

If you make your entry point (main.ts) a platform-specific file (main.ios.ts and main.android.ts), the webpack compilation will fail. The compilation also fails when the entry point of a linked plugin is a platform-specific file (take a look at the related issue).

What is the new behavior?

The platform-specific files are supported entry points of your app and the linked plugins.

Related to: #612

[rynop]

Hi @DimitarTachev - do you have a rough idea when v0.22.0 will be released to NPM? There is another OSS lib that Robert and I are working on that depend on it (ref'd above). Thanks for all your work on this lib.

[DimitarTachev]

Hi @rynop, the development for 0.22.0 is already frozen, if we don't find blocking issues in our testing phase, you can expect the rc release till the end of the day and an official 0.22.0 release till the end of the next week. Meanwhile, you can access this fix using our next tag (nativescript-dev-webpack@next).

P.S. The 0.22.0 release is synchronized with NativeScript 5.4.0.