Change NewPostView to NewPostScreen to make it route based

[geovnn]

As discussed in #1119

Changes:

• Moved NewPostView to NewPostScreen and replaced Dialog with DisappearingScaffold
• Previous conditional call to NewPostView now start the navigation to the route passing the hexid of the baseReplyTo, quote, fork, version and draft parameters
• accountViewModel.getNoteIfExists(hex) is called to retrieve the parameters
• Fixed imports which used stuff from the NewPostView file

[vitorpamplona]

Very cool! As we move forward, it's likely that we will need to have a newPost screen for every event kind with only the functions associated with them. Do you think we should build multiple routes or just one with parameters? Multiple routes feel more organized.

[geovnn]

That make sense, the only drawback would be if you need to pass complex entities around, but that can be solved passing ids as navigation arguments. I think the benefits of an easier code outweights the drawback.

[vitorpamplona]

Yeah, but we can switch to the new Route system that passes full objects as jsons, like this: https://www.youtube.com/watch?v=AIC_OFQ1r3k

[geovnn]

Cool, didn't know about this!