Add generic notification subscriptions through webhooks

[sdelgadoc]

No description provided.

[kwilsonmg]

I think that this is a cool concept, but perhaps it could be extended to work for folders other than inbox as is currently hardcoded? I think that that would make it more extensible/useful. What are your thoughts, @sdelgadoc?

Edit: I see that sdelgadoc is potentially inactive. @alejcas what are your thoughts on this PR as a whole? If it's accepted I would be happy to put in a PR then doing the above.

[sdelgadoc]

Hey @kwilsonmg, I never finished this, but still find it useful to implement. There's also some ways I've figured out how to make it more robust. If @alejcas and you would find it useful, I could finish it and submit. Let me know!

[kwilsonmg]

I have immediate use cases in mind as well for a feature like this. Curious alejcas' thoughts. I would love to see this completed.

[alejcas]

This should be on it's own file (subscriptions.py) and be accessible through the account object. A subscription can be set to any ms graph element. I would like to merge it but not in it's current state.

[sdelgadoc]

Thanks @alejcas, your architectural suggestion makes sense. Give me a few days and I'll send out a PR with the changes for @kwilsonmg and you to test and review.

[sdelgadoc]

Hey @alejcas and @kwilsonmg, please find here completed the PR to add subscriptions and notifications to the library. I added an example to demonstrate usage, and for testing. Let me know if you have any questions or edits. Otherwise, this is ready to merge.

[alejcas]

I can merge it as it is although it lacks:

• list subscriptions
• get subscription
• update subscription

At least the list method should be available.
But as said I can merge this and latter on improve. As you want.

[sdelgadoc]

Thanks @alejcas. I think that adding the three endpoints you listed is reasonable. However, with the holidays coming up, I will likely not be able to start implementing until early to mid December. So, depending on @kwilsonmg and other users' timeline, we can either merge this PR to give folks basic functionality, and I can add the additional endpoints later, or wait and merge all the functionality together in a few weeks. Either works for me.

[kwilsonmg]

This is certainly a "nice to have" for the library, but I can honestly wait a while longer. I'm not in a huge rush, just excited by the possibilities this will all unlock once completed. (TLDR: I'm indifferent)