(cherry picked from commit 3e676f97)

Job status in the historic database will not change if the job is in a finalized status COMPLETED FAILED and is changing to a starting status WAITING READY

Improved platform retrials, submission detection fix , wallclock fix, bad parameters error was wrongly put as error to live ( Due debug )

Fixed bug with submission when a job fails, now only reconnects to one platform. Now scheduler not configured correctly is applied to all platfomrs

fixed issues when forcing proj and jobs from templates

Implementing #644. Job ordering has been implemented, the ordering principle follows date -> member -> section -> chunk.