Allocation: Add more complexity to EULA agreements

[dsajdak]

We've added some basic updates to allocations with End User License Agreement (EULA) attributes on them in PR #539. This includes displaying the EULA on the allocation detail page and reminding the manager when new users are added to an allocation that they should be made aware of the EULA. However, there are some centers that want a more robust process that requires the users on the allocations themselves to login, review, and accept the EULA before they are given access to the resource. If they decline to accept the EULA, their allocation status changes to 'declined' and they are not given access to the resource. This will involve:

• changing the user's allocation status to something other than 'active' as they move through this process: if the allocation has a EULA attribute on it, new users that get added to it are in the 'pending' status
• sending the user an email notifying them that they need to complete this step
• sending the user an email reminding them after a given time if they don't complete it (should be configurable like the other email features)
• sending the user an email when they complete the process so they have proof it was done, cc'ing the managers on the project
• changing the user's allocation status to 'active' once they've completed the EULA review
• change the user's allocation status to 'declined' if they decline to agree to the EULA
• ensure that this does not affect any other allocations that a user might be added to at the same time
• This should be a configuration option for centers that want an advanced EULA process.

There are many possibilities and complications for this type of a process. This particular feature should provide the expanded capability of requiring a user to agree to a EULA but will not cover all possibilities. Future users of ColdFront can use this feature to model more complicated processes or expand on this feature, if desired.