feat(divider): add new divider component

[esraltintas]

Add new divider component

Pull Request

Description

Describe your changes (or add ticket description) and add relevant screenshots

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation change

How do I test this

• Add steps to test
• in bullet point format
• preferably you can add link to the storybook build in the PR

Checklist

Did you remember to take care of the following?

• npm i – for new NPM dependencies.
• npm run lint - to check for linting issues
• npm run test - to run unit tests
• npm run test:sh:docker - to run screenshot tests, detail instruction

New Feature / Bug Fix

• Run unit tests to ensure all existing tests are still passing.
• Add new passing unit tests to cover the code introduced by your pr.

Thanks for contributing!

[github-actions]

Pull Request Test Coverage Report for Build 5256142633

• 5 of 5 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 92.224%

---

Totals
Change from base Build 5212697865:	0.02%
Covered Lines:	1671
Relevant Lines:	1735

---

💛 - Coveralls

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	96.1%	1872/1948
🟢	Branches	81.21%	523/644
🟢	Functions	82.56%	161/195
🟢	Lines	96.31%	1671/1735

Show new covered files 🐣

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / Divider.tsx	100%	100%	100%	100%

Test suite run success

402 tests passing in 57 suites.

Report generated by 🧪jest coverage report action from 1cd362b

[github-actions]

Compiled a new version demo.

[coveralls]

Pull Request Test Coverage Report for Build 5256142633

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 5 of 5 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 92.224%

---

Totals
Change from base Build 5212697865:	0.02%
Covered Lines:	1671
Relevant Lines:	1735

---

💛 - Coveralls