[Workstreams] remove support for creating phases for new projects

[maxceem]

This is part of #315

For the purpose of easy development purposes currently I've updated project create endpoint so it can create projects with phases (old) or workstreams (new) depend on the project template phases/planConfg.

So if the planConfg has property, workstreamsConfig we create workstreams for the project.
Otherwise, we use our old way and create phases.

@vikasrohit I'd like to confirm a few things:

1. Should we completely drop the support phases for new projects (we keep it for old)
2. If some template doesn't have workstreamsConfig provided should we create some default workstream or keep it empty? (before you proposed both options, for now I don't create any workstreams if there is no config).
3. If some template HAS workstreamsConfig provided but due to project details no workstream is selected. Should we keep the list of workstreams empty or also create some general one?

[vikasrohit]

So if the planConfg has property, workstreamsConfig we create workstreams for the project.
Otherwise, we use our old way and create phases.

Yes. That was my intent as well, however, I am thinking of simple way now. If we have workstreamsConfig, create workstreams based on the config, otherwise just leave the project plan empty. Specifically, answering to your quesitons:

1. Yes, it means we won't create any phases on project creation for any project template because we don't want to continue with static mapping between templates and phases which we have right now in phases config of a project template.
2. No default work stream should be created
3. Empty workstreams i.e. no default work stream should be created

[maxceem]

As was discussed here appirio-tech/connect-app#3258 (comment) I've updated the current logic, so it's like this now:

1. If for project template workstreamsConfig is defined, then project would support workstreams, we set details.settings.workstreams and create workstreams if any are defined.
2. If for project template workstreamsConfig is not defined, it works as before and let us create phases. If project has predefined list of phases they would be automatically created.

So in total we fully support both ways of creating project for now, using phases and using workstreams.

PS. I propose to close this issues until we fully move to workstreams. After that we can think about removing logic for creating new projects with phases.

[vikasrohit]

@maxceem on thinking more I realized that we will never need to support the phase creation on ne project creation. What we need as backward compatibility, is to let users add phases to their running projects. And I think the support we have applied here applies only for the project creation time. So, we just need to ensure that we allow addition/removal of the phases for existing projects which don't use work cards.
Let keep this on hold for some time, until we get some clarification on the work card implementation.