Control login timing to avoid "NOT AUTHENTICATED" error due to simultaneous logins.

[mzsmakr]

Feature to control login timing added to avoid simultaneous logins. This feature is effective from multiple instances too if you set different LOGIN_SEC in each instances. With this feature, we can specify when to login accounts specified in LOGIN_SEC. The number should be between 0 - 60. Default is tuple(range(1,60)), so accounts login every second. With this feature, NOT AUTHENTICATED error due to temp IP ban will be avoided.

I tested in following conditions.

• 2000 workers
• 100K spawnpoints
• 16 instances
• Single residential IP address.

Tested for over 10 days and haven't observed single NOT AUTHENTICATED error. I also tested with single private proxy and achieved same result (no NOT AUTHENTICATED error)

# Control login timing exactly set in LOGIN_SEC if LOGIN_SEC_CONTROL = True.
# Too many simultaneous logins from single IP address easily causes temp IP ban 
# and results in "NOT AUTHENTICATED" error.
# Even you set SIMLTANEOUS_LOGINS = 1, temp IP ban will happen if you run multiple instances.
# If you set different LOGIN_SEC for each instances, you can avoid simultaneous logins from
# multiple instances.
# Example:
#   instance A: LOGIN_SEC = (1,11,21,31,41,51) 
#   instance B: LOGIN_SEC = (4,14,24,34,44,54)
#   instance C: LOGIN_SEC = (7,17,27,37,47,57)
# Even single instance condition, default LOGIN_SEC is helpful to control login.
# It is recommended to set SIMULTANEOUS_LOGINS = 1 if you turn on LOGIN_SEC_CONTROL
# Default is False.
# Ignore this config, if you use many proxies and not have issue for simultaneous login.  
#LOGIN_SEC_CTRL = False
#LOGIN_SEC = tuple(range(1,60))

[Sanake]

please merge this