[CLID-256] Rebuild catalog refactorings

This user story is to cover all the scenarios that were not covered by ~~CLID-230~~

links to

1.	Remove the builder container file in case the image size does not shrink	Closed	Unassigned
2.	Reduce the number of arguments from NewBuilder	Closed	Sherine Khoury
3.	Save the container file used to generate the filtered catalog in the working-dir	Closed	Alex Guidi
4.	Check the feasibility of reusing the catalog already in the working-dir	Closed	Sherine Khoury
5.	Rebuild of the catalog outside the collector	Closed	Sherine Khoury
6.	Create a different interface for the RebuildOfCatalogs	Closed	Sherine Khoury
7.	Save the error of the rebuild of catalog in the working-dir	Closed	Alex Guidi
8.	Only add the buildah options that are different from the default	Closed	Alex Guidi
9.	Generate folders in the working-dir based on the filtered catalog digest	Closed	Alex Guidi
10.	Check the need of hard coding archs	Closed	Alex Guidi
11.	Remove related images when the catalog rebuild fails	Closed	Unassigned
12.	Common func between operator collector and rebuild catalog to define destination	Closed	Unassigned
13.	Change the tool to rebuild catalogs	Closed	Sherine Khoury
14.	Manage rebuilding OCI catalogs	Closed	Luigi Mario Zuccarelli
15.	should build store location remain the default?	Closed	Luigi Mario Zuccarelli
16.	Waiting for catalogs to get collected, then to be rebuilt is long	Closed	Sherine Khoury
17.	M2M catalogs are getting rebuilt more than once	Closed	Sherine Khoury
18.	Delete feature is still using the old operator-images dir structure	Closed	Alex Guidi
19.	add a copy of the imagesetconfig in the tar archive	Closed	Luigi Mario Zuccarelli

There are no comments yet on this issue.