Added a header component

[Rohanhacker]

Fixes #47

Checklist

• I have read the Contribution & Best practices Guide and my PR follows them.
• My branch is up-to-date with the Upstream master branch.
• I have added/updated necessary tests/documentation (if applicable)

Changes proposed in this pull request:

• created a Header component

[Rohanhacker]

Just created a container and didn't added option to add/remove avatar, search and stuff because header component is different for different pages. 😜

[blenderskool]

@Rohanhacker Please check the design guidelines again. Yes, the header component behaves differently in different pages, but in a specific format.

Please include additional styles for search/back icon, avatar, and other use cases.

[Rohanhacker]

@blenderskool I think we should have different header component for different headers which all use a common base header component

[Rohanhacker]

@blenderskool We should do it in similar way as ant design does.
https://ant.design/components/layout/#components-layout-demo-top

[palnabarun]

@Rohanhacker Updated the PR description to include the relevant issue.

[blenderskool]

@Rohanhacker Looking at the docs, I feel default AppBar in Material UI with some overrides can be used. Overrides include:

• box-shadow

There isn't any other type of header used in the mobile design as of my knowledge

[Rohanhacker]

@blenderskool by different header I meant one with avatar, one with just back btn etc

[Rohanhacker]

@blenderskool I agree material-ui's default components can be used with some override

[blenderskool]

@Rohanhacker Those differences are all in a general component. I think we can pass those changes as children. Let's see how it works out while developing individual pages 🙂