Android replaceInFile

[davidgovea]

addresses #1060

Rebased the old POC up to master -- figured I'd create the PR to help discussion.

With iOS's plugin processing, the 'hull filling' happens first. In android, it seems to happen after the plugin processing, so we need to defer the replacements.

The fs use and replacement function was lifted from the iOS implementation, but was then wrapped in an async function side-effect creator for later processing. This is probably inefficient, but I held back on optimizations, pending discussion.

[belemaire]

@davidgovea
I'm good with this implementation.
The processing in two parts is not ideal, but that's due to the current class design.
These generators classes are anyway overdue for refactoring, so we will clean things up a bit soon hopefully, that's why I'm not too concerned at this point.

Could you just make the async replacement functions non async. Looking at the implementation, there is no await in the anonymous function body, and it's only making fs sync calls so there is nothing async here ;) So just update the replacements typedef, remove async and await when you invoke each function in the for loop.

Then could you just please squash your commits to a single one :)

[davidgovea]

@belemaire updated & squashed

[belemaire]

Thanks 👍