Importing Azure function into IntelliJ via Maven results in broken state project

Transfer from https://github.com/JetBrains/azure-tools-for-intellij/issues/578 reported by @alexandrunechifor.

Importing a Maven(Java) azure function generated with IntelliJ into another instance of intelliJ results in a broken state for the imported project as the function module is not found in run configurations(error: please specify a module).

Steps to reproduce
1)generate an Azure functions project with IntelliJ
2)remove .idea and .iml files - this often happens when committing to git - not everyone is using IntelliJ and these files should not be relevant when someone else tries to import the project, even in another instance of IntelliJ
3) import project in IntelliJ as maven project and experience the following results:

• project cannot be built/run after import from IntelliJ
• maven cannot find properties definitions
• "module" field is not present and cannot be added when trying to add an Azure Function Run configuration

Being able to import an Azure Functions project independently of the existence of .idea and .iml files is crucial for collaborative development for many teams.

Thank you.

Reproduce the issue by generating an Azure Functions Java project, removing the .idea and .iml files, and importing it as a Maven project in IntelliJ. Inspect the project import and Azure Function run-configuration flow, including Maven property resolution. Done means the imported project builds and runs, Maven properties resolve, and an Azure Function run configuration can select its module without those files.