Move old yammer recipe to /viva-engage

[marrws]

Pre-flight Checklist

Please ensure you've completed all of the following.

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I updated the version package Updating

Description of Change

February last year Microsoft renamed Yammer to Viva Engage ¹ and the old yammer.com now redirects to https://engage.cloud.microsoft. This change moves the old /yammer recipe to /viva-engage and refactor the selector for notifications and messages.

Maybe the hasIndirectMessages should be set to false because for my organization this notification pops-up for every internal announcement, not only for private/direct messages. I leave that decision to you guys.

Footnotes

1. https://www.microsoft.com/en-us/microsoft-365/blog/2023/02/13/yammer-is-evolving-to-microsoft-viva-engage-with-new-experiences-rolling-out-today/ ↩

[vraravam]

@all-contributors please add @marrws for code

[allcontributors]

@vraravam

I've put up a pull request to add @marrws! 🎉