Adds an icon in password field when entering a password protected meeting, which shows what has been entered so far.

Closes feature request #8635.

For the third pull request we came up with the issue ourselves. We noticed that sending private messages in the Jitsi chat was a unintuitive process. Thus we introduced the ability to send private messages to a meeting participant by entering a @ (at) sign followed by the name of the desired receiver. By typing the first few characters of the name possible suggestions are shown that the sender can choose from to auto-complete the name. After this a small popup in the chat appears that a private message will be used and the sender can send the private message. Implementing the feature took longer than expected because of the complexity of the chat system and the related components.

Because of the extra time it took with the merging of the other pull requests and the difficulties we had with getting the final code up to the standard that a big program like Jitsi Meet requires, we did not have enough time to finish the pull request. Therefore no feedback from the community could be received for this feature regrettably.

When implementing code highlighting, I noticed there was also no Markdown support (such as .. for italic and such). I saw an issue opened earlier for this but it went stale and was automatically closed #5536 Therefore I decided to hit two birds with one stone and implement a markdown parser (and thereby implement code highlighting for the chat as well).

Closes #4515, #5536 (which has gone stale)

The developers in the bi-weekly community meeting were very enthusiastic about our idea of adding the architecture overview to their handbook. We decided that for the 4th essay we would combine the writing of the essay with the creation of the architecture.md. The handbook entry contains an overview of the components in both text and a graph format, a code map, and a description of the testing environment. Feedback about the content was discussed in the bi-weekly community meeting, on the community forum, and about the form of the submission in the pull request. We adapted the text and picture to fit most of the received feedback.

After repeated attempts from us to get the Jitsi team to review our updates to their handbook, they did. However, the time between a review and the changes we make is very long. Therefore the pull request is still waiting to be merged in the Jitsi-handbook repository.

This Pull Request adds Dutch tranlsation for the main language file in " lang/main-nl.json". The Dutch language file of the Jitsi Meet project was not very up-to-date with translations as not many Dutch developers work on the project. That’s why it was decided to update the language file with the missing language strings as a pull request. Most of the missing language strings were from relatively new features.

The pull request was merged quickly without any comments about possible changes.