Fix Path tool not displaying its hints during G/R/S modes

[AustinHen]

Closes#3537, also reported at https://discord.com/channels/731730685944922173/881073965047636018/1419968518086197269

Previously the path tool hints would override the hints from other operations (Eg GRS's hints would not show. This was the case for everything but the drag) It was just an order of operations issue. When "update_dynamic_hints" was created (replacing "update_hints"), the path tool updates would always happen after the other tools' hints. This means that, when you are in GRS, the GRS hints will be written and then immediately overwrite. Sending ToolMessage::UpdateHints() after updating the path tool's hints fixes this.

[AustinHen]

an alternative would be to call responses.add_front(FrontendMessage::UpdateInputHints { hint_data }); as opposed to responses.add(FrontendMessage::UpdateInputHints { hint_data });

[Ezbaze]

Tested. Works as expected.

Video:

pr3222.mp4

CC @Keavon

[Keavon]

Thanks for this contribution. Please leave a comment with this issue number in the issue #3537 so I can assign it to you after you've posted the comment over there.

[Keavon]

Hi @AustinHen, thanks again for this code contribution to the project! We're still hoping you will respond to the request to relicense this code. Please see #4208 ASAP, thank you!

[Keavon]

Hi @AustinHen, we're grateful of your past code contribution to Graphite, but unless we hear from you by the end of this weekend with agreement about relicensing your code to include the MIT license, we will begin steps to remove your code contributions so that you will no longer be a Graphite code contributor. We'd much rather avoid this outcome, so please respond now.

To agree, simply log into your GitHub account, visit #4208, and copy-paste this into a comment:

"I license my past and future contributions to Graphite under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option."

If you're hesitant because you disagree or have questions, feel free to respond with another message; we'll do our best to answer your questions or concerns. More explanation is at the top of the linked thread if you're confused. So far, 164 contributors have agreed and you are among the 11% remaining whom we are still hoping to hear from before we begin removing your code from the project starting this Monday. (If you only see this later than Monday, your future belated response will still be appreciated.)

Thank you for your cooperation and support of open source, and we hope you'll help us keep your valued contributions in-tact.