Improve annual subscription handling with user provisioning

Summary

By default, when Cloud products have an annual subscription, it blocks new users to be added if it is going to be exceeded, which is expected to prevent an impact on the product's functionality.

However, if users are being pushed to the products via user provisioning, it will allow the license to be exceeded, which will trigger the following symptoms:

• Even though users already have a license to the product, they won't be able to be added to groups that have product access to it.
• New users cannot be added manually unless users with licenses are already removed.
• Applications like Confluence will not allow space details to be edited

Suggestion

Similar to the monthly plan, where the tier is automatically upgraded based on the number of users with licenses in use, this is a suggestion to improve how the licensing is handled when user provisioning is in use.

Some examples:

• Send emails to administrators stating that the license is exceeded, providing options to reduce the number of users before blocking certain functionalities for the products.
• Similar to what happens when an admin tries to manually add a user to a subscription that reached its limit, block users to be added via user provisioning.