feat(deriv_ui): [MOBC-740] move UI related packages to deriv_ui

[behnam-deriv]

Clickup link: https://app.clickup.com/t/20696747/MOBC-740

This PR contains the following changes:

• moving deriv_banner to deriv_ui
• moving deriv_date_range_picker to deriv_ui
• moving deriv_expandable_bottom_sheet to deriv_ui
• creating example app for deriv_ui and including the example app of above packages in it
• moving test cases of above packages to deriv_ui

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

Pre-launch Checklist (For PR creator)

As a creator of this PR:

• ✍️ I have included clickup id and package/app_name in the PR title.
• 👁️ I have gone through the code and removed any temporary changes (commented lines, prints, debug statements etc.).
• ⚒️ I have fixed any errors/warnings shown by the analyzer/linter.
• 📝 I have added documentation, comments and logging wherever required.
• 🧪 I have added necessary tests for these changes.
• 🔎 I have ensured all existing tests are passing.

Reviewers

@ahrar-deriv @sahani-deriv

Pre-launch Checklist (For Reviewers)

As a reviewer I ensure that:

• ✴️ This PR follows the standard PR template.
• 🪩 The information in this PR properly reflects the code changes.
• 🧪 All the necessary tests for this PR's are passing.

Pre-launch Checklist (For QA)

• 👌 It passes the acceptance criteria.

Pre-launch Checklist (For Maintainer)

• [sahani] I make sure this PR fulfills its purpose.

[sahani-deriv]

this later needs to be moved to deriv_localizations right?

[behnam-deriv]

Yes

[sahani-deriv]

I suggest we have one example app for all the ui components. For example we might have a list of components name and when we click on it we can view the component or something like this. If we all agree, this might be a work for another sprint.

[ahrar-deriv]

think it is best we re-arrange the structure as we now have multiple widgets in different categories. so the top folder should not be presentation/widgets. we should move all one level up and each category has its own presentation layer with widgets inside and core ....

[behnam-deriv]

I suggest we have one example app for all the ui components. For example we might have a list of components name and when we click on it we can view the component or something like this. If we all agree, this might be a work for another sprint.

Yes I agree. Gradually this is what we want to achieve. to have a single example app to showcase all the UI components.

[behnam-deriv]

think it is best we re-arrange the structure as we now have multiple widgets in different categories. so the top folder should not be presentation/widgets. we should move all one level up and each category has its own presentation layer with widgets inside and core ....

I created a component category to include compound widgets that are not as simple as a single flutter widgets. we can discuss it further to reach a clean folder structure in deriv_ui

[sahani-deriv]

how about moving these to docs folder and linking it in the main readme?

[behnam-deriv]

I suggest we keep it in the same folder as it will be easier for clients to find the relevant files of the README they are reading. for general docs we can move it to docs folder.

[sahani-deriv]

i think later we should use one localization class for all the components.