[#258] Update the base template structure to follow the Clean Architecture folder structure

[doannimble]

• Solves #258

What happened 👀

Our current template base structure under lib/ folder is not up to date with the Clean Architecture folder structure. There is no clear separation between the data, domain, and presentation layers. Also, the current structure does not fully follow the Clean Architecture components naming. Therefore, the project outcome lacks a sound foundation to commence development.

Insight 📝

• [x] Create core, app, domain, data folder
• [x] Move response, api service, repository_impl to data
• [x] Move view model, state, screen to app
• [x] Move network exception to `core_errors``
• [x] Move models, repository_abstract, usecases to domain
• [x] Update the mapping model from response
• [x] Update unit test
• [x] Refactor package dependencies paths

Proof Of Work 📹

The template is able to be built normally.

[luongvo]

@doannimble please rebase to clean up merge commit, and add necessary meta info for this PR 🙏

[doannimble]

@luongvo Rebased. Please let me know if we need to add more necessary infor 🙏

[luongvo]

@doannimble why do we have some commits tagged with #169 task in this PR? 🤔 If they belong to this #258, could you please "reword" them?

[manh-t]

@doannimble We currently do not have any files in the data/remote/models/requests directory, so it has not been created. Would it be possible to create a .keep file in the directory to ensure it appears in our template? This is a practice from react-template 😄

[luongvo]

@doannimble We currently do not have any files in the data/remote/models/requests directory, so it has not been created. Would it be possible to create a .keep file in the directory to ensure it appears in our template? This is a practice from react-template 😄

Possible, nice suggestion imo cc @doannimble

[doannimble]

@manh-t Good to know, I've updated. cc @luongvo