Update to iTwin 4.7.2 (and newer appui)

[tcobbs-bentley]

For some unknown reason, this caused our three remaining class-based React components to fail to compile, so those were converted to functional components.

[tcobbs-bentley]

@toddsouthenbentley Please carefully review the class to functional React component conversions. I think I tested them, but I'm somewhat uncomfortable about things like the fact that the useEffect in TouchCaptor triggers every time isTouchStarted changes. It needs to do that, but since that removes the old listeners and creates new ones, I'm a little leery of it.

[toddsouthenbentley]

@toddsouthenbentley Please carefully review the class to functional React component conversions. I think I tested them, but I'm somewhat uncomfortable about things like the fact that the useEffect in TouchCaptor triggers every time isTouchStarted changes. It needs to do that, but since that removes the old listeners and creates new ones, I'm a little leery of it.

It looks like appui-react now has a usePointerCaptor hook that works for both mouse and touch events. I would suggest using that and getting rid of the Touch* classes/functions.

If you're still leery of the new code then I'd suggest staying with the old code and figuring out why it no longer builds.

[tcobbs-bentley]

It looks like appui-react now has a usePointerCaptor hook that works for both mouse and touch events. I would suggest using that and getting rid of the Touch* classes/functions.

It's not at all obvious how I would update the code to use that, and it looks like that would be an even bigger rewrite than converting a class to a function.

If you're still leery of the new code then I'd suggest staying with the old code and figuring out why it no longer builds.

I am investigating that, but the reality is that changing the class components to function components is a good thing. Given that everything works (resizing the resizable bottom panels), I think my conversion is correct.

[tcobbs-bentley]

Updating @types/react to 17 seems to fix the problem that prevented class-based components from being used. I can revert the class-to-functional changes, but since they are generally a good thing, I'm a bit hesitant to do so.

[tcobbs-bentley]

@toddsouthenbentley As you noticed, I reverted the components I was leery about to their original class versions after fixing the problem causing the compilation errors. I left ActionSheetButton as a functional component because it was much simpler and I don't have reservations about it.