I read it.
To me, this example suggests that Katalon Team implicitly demands users to edit the build.gradle file to specify the required version of DevTool jar and execute $ gradle katalonCopyDependencies to perform pulling the latest jar.
A problem for users arises here. Usually the users set-up Chrome and other browsers to upgrade automatically when a new version is released. So it is quite likely that, when the browsers are upgraded silently, their Selenium4 based Katalon projects suddently stops working because the version of browser and DevTools-jar mismatches. They might post questions to the forum.katalon.com asking why their tests suddenly stop working. Their problems will repeat for years as long as the versions of browsers continue updated.
How are you, Katalon Team, going to manage this difficulty?
I think that one of the value of Katalon Studio for users is that users are not responsible at all for managing the vesions of dependent jars as long as they use Katalon Studio’s built-in functionalities. Are you going to abandon this value ---- built-in jars are consistently managed by the product – as of Studio 9?
Are you going to ask users to be responsible for the version consistency of DevTools jar and browser? It is not enough if you say “look at this build.gradle example”. Usual Katalon users do not understand Gradle at all. They do not have Gradle installed. Does the Studio 9.x requires users to install Gradle for themselves? Then Katalon Studio will no longer be “All-In-One Test Automation Platform”.