Fixed case if user removes all cycles

[imblowfish]

Fixed #166

In this PR I added possibility to save empty array of cycles. Also I removed isMarkedFutureDays because now we using ion-datetime built-in limitation instead of custom checks

New test has been added #192

[imblowfish]

@IraSoro could you give me rights for peri-tests project or add test #192 by yourself?

[IraSoro]

Read more about this #178 and this #155 .

Firstly, the previous solution did not fix the bug. Below I will describe the steps.
Secondly, you need to leave checking future cycles and editing the current period. The user must be able to edit the current cycle. I missed this in previous PR.

I think that you need to leave the ability to edit the current cycle and leave checking the marked future dates.

[IraSoro]

Steps:

1. We have
   
2. Click Mark button
   
3. Click Edit button
   
4. Dont mark the current date
   
5. Save
   

[imblowfish]

@IraSoro based on steps that you described, looke like you confused this issue with #171
In this issue we just fixing problem when user trying to remove all cycles, but can't do that, because we have datetimeRef value check. I fixed this problem and now you can remove all cycles from the storage.

The problem what you described above is fixed in this PR #196. I checked by myself and everything works fine. And also you can see, that out of 4 commits from #196, 3 are completely duplicates commits from the current PR. And in this PR you can see why we don't need #178 anymore. User should be able to remove all days from cycle, if we'll leave this check then user will not be able to remove the current cycle in case it not finished yet

[imblowfish]

I closed this PR because #196 has the same changs