Predict missing next step when possible

[boogheta]

Sometimes, AN/Senate publish a new adopted text but fail to announce the upcoming step, in those case our data remains stuck to the previous version without including the new text even though it is parsed properly.

For instance here and there : (but this might change further on)

• https://www.lafabriquedelaloi.fr/api/logs-encours/15-securisation_exercice_praticiens_diplomes_hors_ue / http://www.assemblee-nationale.fr/dyn/15/dossiers/securisation_exercice_praticiens_diplomes_hors_ue
• https://www.lafabriquedelaloi.fr/api/logs-encours/pjlf2019 / https://www.senat.fr/dossier-legislatif/pjlf2019.html

The problem is caught there:

https://github.com/regardscitoyens/the-law-factory-parser/blob/master/tlfp/tools/update_procedure.py#L67-L74

But we might want to handle that upper in the chain, for instance after having merged AN & Senate's dossiers, although at this time we do not know for sure yet which steps are echec or not, so not sure...

cf #89

[mdamien]

In the case of the PJLF 2019, I think it's because we remove the predicted hemicycle step in merge.py to keep only the commission step.

the-law-factory-parser/tlfp/merge.py

Lines 148 to 155 in fa6febd

	# Only keep first empty consecutive step as next one to come
	if not dos.get('url_jo'):
	if step.get('source_url'):
	empty_last_step = False
	elif empty_last_step:
	break
	else:
	empty_last_step = True

A simple fix would be to keep the hemicycle step when merging for live texts even when there's a commission step.

[boogheta]

or in this case to not keep commission steps as empty_last_step if the text is using the old_procedure ?