Refactor: Use state from akka-apps for bbb-web API requests

[paultrudel]

What does this PR do?

This PR makes it so that meeting state from akka-apps is used rather than the state from bbb-web to construct responses for isMeetingRunning, getMeetingInfo, and getMeetings API requests. gRPC has been used to facilitate communication between bbb-web and akka-apps.

The classes used for communication through gRPC are defined in the meeting-service.proto file found in bbb-common-message. Both bbb-web and akka-apps extract this definition from bbb-common-message and then generate the required Java and Scala class files. The class files are generated for bbb-web when run-dev.sh is run, but it is also possible to generate the files without running the application by running the gradlew file with the build task. For akka-apps the files are generated by sbt using the compile task.

Motivation

Removal of application state from bbb-web is part of the ongoing process to consolidate application state in akka-apps. Currently when responding to API requests for meeting information bbb-web gets the information from its own internal state when it should rely on akka-apps for this information.

This is the first step in the process of totally removing application state from bbb-web. The next step is to redesign the other APIs such as create and join to not store any state in bbb-web.

[prlanzarin]

@paultrudel Tangential question, out of curiosity: do we plan to extend the gRPC/protobuf usage to the rest of the internal messages/objects defined in the bbb-common-* libraries down the road?
That'd be great.

[paultrudel]

@paultrudel Tangential question, out of curiosity: do we plan to extend the gRPC/protobuf usage to the rest of the internal messages/objects defined in the bbb-common-* libraries down the road? That'd be great.

The current plan is to just replace the internal messages used by the bbb-web APIs to communicate with akka-apps with gRPC, but it is certainly a possibility that, in the future, this can be further extended to the other internal messages as well.

[gustavotrott]

Just a few comments trying to clarify my understanding!

[sonarcloud]

Quality Gate failed

Failed conditions
E Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[github-actions]

Automated tests Summary

✅ All the CI tests have passed!

[github-actions]

This pull request has conflicts ☹
Please resolve those so we can review the pull request.
Thanks.