feat: bootstrap stripe webhook

[davideimola]

🔗 Linked issue

Closes #46
Closes #49

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[davideimola]

@LobeTia this is the first draft I made, check if the flow is respecting what we need.

[TheJoin95]

Why don't we use pending ?

[davideimola]

We have to think about it... I am not sure also it is the right name, but it is something like, when you create a membership it isn't paid yet. So, I think a different status just to differentiate from who's paid and its waiting for approval and other users that they didn't have finished their payment

[TheJoin95]

I'm afraid of having orphans member in these scenario. It could be helpful to have a column per member to identify the payment status as it could be unrelated from the member status as it is a consequence (especially in a renewal case).

To me the waiting status is an over head

[davideimola]

We have lastPaymentAt which ensures the subscription has been successfully paid... I don't know what can be better when we operate with those users.