feat(core): autoreject applications on expiration

[mattjoke]

• scheduler autorejects all of the group application, if the member is switched to EXPIRED state
• setStatus also rejects all group applications for Member

[mattjoke]

I decided to scrap the idea of introducing the logic of the registrar manager to the members manager. Changes:

• removed the logic used before
• The two ways to set the status to EXPIRED and reject applications are as follows
  • setStatus method from API, which will do the rejection (NOTE: any other internal calls of setStatus will not trigger the rejection process)
  • scheduler will do the automatic rejection

PROS:

• same logic and calling the same method will result in the same results
• no immediate and direct update of the database with new SQLs

CONS:

• Internal calls of setStatus may need the rejection of the applications