[core] fix(PanelStack2): animation direction in controlled mode

[invliD]

Fixes #4686

I have a cherry-pick onto v4's renamed PanelStack ready locally (based on #4799, so not pushing just yet).

[blueprint-bot]

Fix PanelStack2 animation direction in controlled mode

Previews: documentation | landing | table

[blueprint-bot]

Fix lint

Previews: documentation | landing | table

[adidahiya]

the gist of the change seems reasonable, but it causes issues when renderActivePanelOnly={false}, the page crashes:

[blueprint-bot]

Fix import

Previews: documentation | landing | table

[invliD]

@adidahiya That crash is actually not caused by this PR. I've found two issues that would cause a crash due to inconsistent number of hooks called:

1. Hooks are called after this early return:
   

   blueprint/packages/core/src/components/panel-stack2/panelStack2.tsx

   Lines 95 to 99 in 55f89fa

   	if (stack.length === 0) {
   	return null;
   	}
   	const handlePanelOpen = React.useCallback(

2. The renderPanel function is called, not added as a JSX.Element. This is the issue the example is running into when using controlled mode (in fact just the 2-line change switching the example to controlled mode reproduces the issue). If a component uses hooks, it must be created as a JSX.Element, otherwise the hook calls are attributed to the parent component. In that case, unless the current panel or all panels together (depending on renderActivePanelOnly) call the same number of hooks, we'll run into that crash.
   

   blueprint/packages/core/src/components/panel-stack2/panelView2.tsx

   Lines 89 to 93 in 55f89fa

   	{props.panel.renderPanel({
   	closePanel: handleClose,
   	openPanel: props.onOpen,
   	...props.panel.props,
   	} as PanelProps<T>)}

   
   I believe the three options we have are either (1) pretend renderPanel is a component and call createElement for it, (2) wrap each renderPanel call in a simple FC that essentially takes ownership of potential hook calls, or (3) break typings of renderPanel to disallow passing of an FC itself, always requiring a function. Not sure that one's possible.

Either way, given that the issue already exists, let's fix that in a follow-up.

[adidahiya]

Filed #4807 for follow-up bug