Inconsistent documentation around Navbar components

[ggdouglas]

There are two ways of referencing/importing <Navbar> sub-components. Either they imported directly from a module or namespaced as an alias off of Navbar itself (similar to the "namespaced" or compound component pattern);

Imported directly:

blueprint/packages/docs-app/src/examples/core-examples/navbarExample.tsx

Lines 19 to 29 in 37e182e

	import {
	Alignment,
	Button,
	Classes,
	H5,
	Navbar,
	NavbarDivider,
	NavbarGroup,
	NavbarHeading,
	Switch,
	} from "@blueprintjs/core";

blueprint/packages/docs-app/src/examples/core-examples/navbarExample.tsx

Lines 53 to 60 in 37e182e

	<Navbar>
	<NavbarGroup align={alignRight ? Alignment.RIGHT : Alignment.LEFT}>
	<NavbarHeading>Blueprint</NavbarHeading>
	<NavbarDivider />
	<Button className={Classes.MINIMAL} icon="home" text="Home" />
	<Button className={Classes.MINIMAL} icon="document" text="Files" />
	</NavbarGroup>
	</Navbar>

Namespaced:

blueprint/packages/core/src/components/navbar/navbar.md

Lines 9 to 14 in 37e182e

	The __Navbar__ API includes four stateless React components:
	* __Navbar__
	* __NavbarGroup__ (aliased as `Navbar.Group`)
	* __NavbarHeading__ (aliased as `Navbar.Heading`)
	* __NavbarDivider__ (aliased as `Navbar.Divider`)

blueprint/packages/core/src/components/navbar/navbar.md

Lines 20 to 27 in 37e182e

	<Navbar>
	<Navbar.Group align={Alignment.LEFT}>
	<Navbar.Heading>Blueprint</Navbar.Heading>
	<Navbar.Divider />
	<Button className="@ns-minimal" icon="home" text="Home" />
	<Button className="@ns-minimal" icon="document" text="Files" />
	</Navbar.Group>
	</Navbar>

blueprint/packages/table-dev-app/src/nav.tsx

Lines 30 to 41 in 37e182e

	<Navbar className={Classes.DARK} fixedToTop={true}>
	<Navbar.Group align={Alignment.LEFT}>
	<Navbar.Heading>Blueprint Table</Navbar.Heading>
	</Navbar.Group>
	<Navbar.Group align={Alignment.RIGHT}>
	<AnchorButton active={isIndex} href="index.html" minimal={true} text="Home" />
	<Navbar.Divider />
	<AnchorButton active={!isIndex} href="features.html" minimal={true} text="Features (Legacy)" />
	<Navbar.Divider />
	<Switch style={darkThemeToggleStyles} label="Dark theme" onChange={this.handleToggleDarkTheme} />
	</Navbar.Group>
	</Navbar>

It seems odd that Navbar is a special case where other components are not organized this way (e.g. Menu). Perhaps we should consider dropping this pattern to enforce better organization/consistency among Blueprint components.