If you run the whole End to End UI Suite every day, the maintenance issues don't get added up. Chrome self-updates about every 1.5 months, and ChromeDriver works for two versions of Chrome. Hence, I don't need to address Chrome-break-tests issues often. (After Selenium 4.12, manages drivers)

From my test automation consulting experience, teams could create a few (maybe up to ~20 UI tests) rather quickly, but they don't run them often and lack the mindset to maintain them. With the increasing number of test execution failures, those 'senior engineers' blame "frameworks" , "test data" or "UI test automation is no need". Check out my article, "Cowardly ‘Automated Testers’ use “GUI Test Automation is hard” as an excuse to avoid, instead do only API Testing", https://zhiminzhan.medium.com/cowardly-automated-testers-use-gui-test-automation-is-hard-as-an-excuse-to-avoid-and-do-only-eefcec5d36d5

The root of the all is very simple. Maintaining Automated UI Tests is a lot a lot harder than creation. Before doing UI Test Automation, which is the foundation of Agile, BTW, get the mindset right. The solution is simple too, as a engineer, "we need to make sure our work is verified by a reliable process", otherwise, what is meaning of the word "Engineering"?

The solution is also simple, just run all UI tests daily as regression testing. Starting with a suite of 2 tests, then 3 tests. When a team find it very challenging on reaching a number (usually ~50, that's the capability threshold), engage a test automation coach.