Make microplan to understand states

[scriptnull]

currently we generate state.json file, when microplan publish is executed.

Whenever we run microplan publish, we need to persist a state inside the init file also. ( may be have a issue url or id, in every plan object ) This will help us match the plan object to a result object in state.json and further enables us to do advanced operations like editing an issue created via microplan.

TODO:

• User should be able to add new issues and republish with the same file. Right now, every time I want to use microplan, I need to create different files and switch between them. This kind of offends microplan's core idea.
• Failed plans in previous publish should be published in this publish.

[scriptnull]

I think, this is little too much for people from Hactoberfest, because there are lot unknown parameters that may arise during developing this issue. So, I am removing the Hacktoberfest label.

We need to think more on this and until that, let's not touch this.