Avoid creating analysis records until --commit

[funnell]

A problem I've encountered is misspecifying application filters can result in a bunch of unwanted analysis records.

What do you think of something like:

1. no --commit

• check tuples for validity
• report how many new analyses would be created, how many unprotected would be run, how many are invalid

3. with --commit

• create new analysis records
• run the analyses

[juanesarango]

Yes, I like this idea. Here we can create some logic to skip analyses creations:

isabl_cli/isabl_cli/app.py

Lines 1478 to 1504 in 78c6c44

	with click.progressbar(
	valid_tuples,
	file=sys.stderr,
	label=f"Creating analyses for {len(valid_tuples)} tuples...\t\t",
	) as bar:
	for i in bar:
	try:
	targets, references, analyses, inputs, individual = i
	# self.validate_species(targets + references)
	self.validate_experiments(targets, references)
	analysis = self._patch_analysis(
	api.create_instance(
	endpoint="analyses",
	application=self.application,
	targets=targets,
	references=references,
	analyses=analyses,
	individual_level_analysis=individual,
	)
	)
	analysis["application_inputs"] = inputs
	created_analyses.append(analysis)
	except (exceptions.ValidationError, AssertionError) as error:
	invalid_tuples.append((i, exceptions.ValidationError(*error.args)))
	return created_analyses, invalid_tuples

And just show a dry-run info of how many analyses exist and how many will be created.
Are you open to work in this PR?

[funnell]

Yeah I'm open to working on this