@patternfly/react-console: Remove unnecessary peer dependencies

[vojtechszocs]

This is a follow-up to kubevirt-web-ui-components issue 136.

Main patternfly-react package declares patternfly and react-bootstrap as regular dependencies, which pulls them into the consuming application's dependency tree.

However, @patternfly/react-console package declares patternfly and react-bootstrap as peer dependencies (in addition to having a peer dependency on patternfly-react, which in turn pulls these two specific libraries as regular dependencies).

Aside from the fact that code in @patternfly/react-console package doesn't link to neither patternfly nor react-bootstrap, this breaks the rule established by main patternfly-react package - treating those two specific libraries as regular dependencies, pulled transitively into the consuming application's dependency tree.

Having too many peer dependencies can snowball into tons of warnings in consuming libraries and/or applications. Let's try not to introduce additional peer dependencies unless we have a compelling reason to do so.

[vojtechszocs]

cc @jeff-phillips-18 @mareklibra

[patternfly-build]

PatternFly-React preview: https://1021-pr-patternfly-react-patternfly.surge.sh

[mareklibra]

Thanks @vojtechszocs , I'm fine with removing these peerDeps as they are provided by patternfly-react.

[coveralls]

Pull Request Test Coverage Report for Build 3493

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 82.131%

---

Totals
Change from base Build 3486:	0.0%
Covered Lines:	3968
Relevant Lines:	4569

---

💛 - Coveralls

[tlabaj]

LGTM

[tlabaj]

LGTM