fix(plugin-meetings): remove logs and circular dependency with voicea

[mkesavan13]

PARTIALLY COMPLETES SPARK-515520 and FULLY COMPLETES SPARK-523031

This pull request addresses

• PII Information is being logged from Voicea
• There are Circular Dependency between Voicea and Meetings because of using TriggerProxy in Voicea

by making the following changes

• Removed Circular Dependency by getting rid of TriggerProxy usage in Voicea
• In plugin-meetings, again got rid of TriggerProxy and started logging in place

Change Type

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation update
• [ ] Tooling change
• [x] Internal code refactor

The following scenarios where tested

• Tested all the Voicea-based events for Closed Captions
• Ensured sample app is working fine for the newest changes and that the user-facing events are emitted appropriately
• Checked logs through Sample applications for any of the Voicea events not logging any Payload/PII information

I certified that

• [x] I have read and followed contributing guidelines

• [x] I discussed changes with code owners prior to submitting this pull request

• [x] I have not skipped any automated checks

• [x] All existing and new tests passed

• [x] I have updated the documentation accordingly

---

Make sure to have followed the contributing guidelines before submitting.

[mkesavan13]

Question. Which object has the trigger() function?

@sreenara - The trigger() and emit() comes from AmpState plugin