Added Page Component to make padding across pages to be consistent

[GokulramGHV]

Proposed Changes

• Fixes Implement Page component to make padding across pages consistent #4375

@coronasafe/care-fe-code-reviewers @coronasafe/code-reviewers

Merge Checklist

• Add specs that demonstrate bug / test a new feature.
• Update product documentation.
• Ensure that UI text is kept in I18n files.
• Prep screenshot or demo video for changelog entry, and attach it to issue.
• Request for Peer Reviews
• Completion of QA

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
care-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 22, 2023 at 0:02AM (UTC)

[netlify]

✅ Deploy Preview for care-egov-staging ready!

Name	Link
🔨 Latest commit	3edae85
🔍 Latest deploy log	https://app.netlify.com/sites/care-egov-staging/deploys/63cd25343e1e0e0008c0434c
😎 Deploy Preview	https://deploy-preview-4584--care-egov-staging.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

❌ Deploy Preview for care-net failed.

Name	Link
🔨 Latest commit	040a286
🔍 Latest deploy log	https://app.netlify.com/sites/care-net/deploys/63c27d3b35be7d00098b85ff

[github-actions]

👋 Hi, @GokulramGHV,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
1.3% Duplication

[github-actions]

👋 Hi, @GokulramGHV,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

[rithviknishad]

@GokulramGHV this would be hard to review + I'm pretty sure the merge conflicts would never settle for this PR since there'll always be PRs that'll be modifying the contents of the children of the page.

Ideally what should have been done is, to implement the Page component in one PR and use it in one place so that it can be tested. Once tested and merged, make multiple parallel PRs that use the new Page component for all the different pages.

This would be easier to review + easier to deal with merge conflicts.

cc: @khavinshankar

[GokulramGHV]

@rithviknishad Hey, that's actually a great idea! I'll close this pr and make a new one just with the Page component implemented in one of the pages.