fix: Detect Vaadin projects if dependencies are updated

[MarcinVaadin]

Currently Vaadin dependencies were detected only on post-startup activity. It might cause race condition between this event and indexed / refreshed module libraries.

This PR uses ModuleRootListener to detect library updates together with PostStartupActivity.

If project is indexed already by IntelliJ, ModuleRootListener is not triggered and PostStartupActivity detects Vaadin properly.
If new project is created, PostStartup happen before module is fully loaded with all dependencies and we need to use ModuleRootListener to detect Vaadin.

[github-actions]

Artifact build on last commit: distributions.zip.
For MacOS users: there is a zip inside this zip and Finder unzips them both at once. Use unzip distributions.zip from Terminal or check solution for Archive Manager.

[czp13]

1. Created a new Spring Boot project.
2. Updated the pom.xml to include Vaadin.
3. Then, I saw the following popups:

4. The application started without any issues.

❓ I didn't see any specific message saying, "You have a Vaadin project, Vaadin plugin enabled," or something similar. I expected to, but it's probably fine this way.

So not sure where I could see, or check this log message:

   LOG.info("Vaadin detected in dependencies of " + event.project.name)

[MarcinVaadin]

@czp13 If you see those popups it means plugin has started because Vaadin project has been detected. So it's ok.

[czp13]

@czp13 If you see those popups it means plugin has started because Vaadin project has been detected. So it's ok.

Okey,thanks :), then I will approve it if soonish no one else approves.

[mgarciavaadin]

Tested with the weirdest project structures I could imagine and working perfectly. Good Job!