Added auto book feature

[Nikita-Smirnov-Exactpro]

No description provided.

[OptimumCode]

I believe that we don't need to provide the ability to specify the exact time for a book. This is auto functionality. So, I think it just should create a book with the current time (if the book does not exist).
A user always can call the endpoint to create a book with the time he or she needs.

[Nikita-Smirnov-Exactpro]

OK, it sound like correct but I think admin-tool should create book with time now - 1 hour and create a first page with the same date because schema can contain other active conns which can be started before admin-tool.

[OptimumCode]

Then maybe this is the problem in the schema. The cradle admin should be deployed before other components. Also, you always can create a book in the past using REST API in case there are events/messages from components that were deployed before cradle-admin...

[Nikita-Smirnov-Exactpro]

Then maybe this is the problem in the schema. I don't think so, because by the th2 concept order of component starting doesn't matter.
REST API is complicated way when you need the simplest book to start work.
I try to solve start on a virgin machine problem by this change.

[OptimumCode]

I don't think so, because by the th2 concept order of component starting doesn't matter.
We have a problem then because the order does matter)) What if the cradle-admin will be started after 1 hour + 1 second after the first component produces event/message? We still will have the problem that there is no book that matches the event/message time.
We don't make our and users' lives easier by saying let's just substruct an hour or please, set the exact time you need for the book in config. The only solution to the problem is to start cradle-admin before other components. Otherwise, we are doomed to face that potential problem again and again.

[Nikita-Smirnov-Exactpro]

Your statement is true when CR cradle-admin doesn't exist at the start environment moment or it has critical problem in configuration and user doesn't check environment.
In fact, user can have a problem event infra will start cradle-admin at first. We can solve part of problems when infra will find all book mentioned in schema and doesn't create estore / mstore queue until books have been created

[OptimumCode]

You can use @JsonNaming annotation on the class with PropertyNamingStrategies.KEBAB_CASE