Back office events

[bsoniam]

Store in the DB the following events:
API_ACCOUNT_CREATION
API_ACCOUNT_DELETION
GET_DETAILS
LOCK_ACCOUNT
UNLOCK_ACCOUNT
INIT_PASSWORD
& restructuring the event module and component

[coveralls]

Pull Request Test Coverage Report for Build 252

• 187 of 187 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.6%) to 91.671%

---

Totals
Change from base Build 231:	0.6%
Covered Lines:	1618
Relevant Lines:	1765

---

💛 - Coveralls

[fperot74]

In component.go, we don't want to many business unrelated code in our functions. We should try to have the less "invasive" code as possible here. Could we create functions like :

var event map[string]string = events.CreateEventMap("API_ACCOUNT_CREATION")
events.AddEventValues("realm_name", realmName, "user_id", user.Id, "username", user.Username, "origin", "back-office", "audit-time", time.Now().UTC())

and somewhere else :

func CreateEventMap(apiName string /* and other generic parameters... */) map[string]string {
    event["ct_event_type"] = apiName
    event["origin"] = "back-office"
    event["audit_time"] = time.Now().UTC().Format("2006-01-02 15:04:05.000")
}
func AddEventValues(eventNfo map[string]string, values string...) {
    // can automatically ignore key/value when value is nil
}
func AddEventTime(eventNfo map[string]string, fieldName string, time time.Time) {
}

To illustrate what is worrying me, the initial DeleteUser function is only 2 lines long to do what it is aimed to but is more than 20 lines with code not related to user deletion.