[VO-1120] refactor(FolderPicker): Use ListItem instead File

[cballevre]

This decouples the display of the file table from that of the FolderPicker modal. This will allow you to change the lines as Link in the table in order to take advantage of the default mechanisms of browsers

### 🔧 Tech

* Update filesize from 3.6.1 to 10.1.6
* Update cozy-client from 48.25.0 to 49.8.0
* Update cozy-intent from 2.22.0 to 2.23.0

Related PRs :

• [VO-1120] feat(ListItemSkeleton): Add gutters property to mock ListItem behavior cozy-ui#2709

[bundlemon]

BundleMon

Files updated (6)

Status	Path	Size	Limits
✅	public/drive.(hash).js	1.56MB (+1.56KB +0.1%)	1.7MB
✅	services/qualificationMigration/drive.js	282.15KB (+1.32KB +0.47%)	500KB
✅	vendors/drive.(hash).js	1.79MB (+1.31KB +0.07%)	2MB
✅	services/dacc/drive.js	263.08KB (+1.25KB +0.48%)	500KB
✅	app/drive.(hash).js	161.61KB (+80B +0.05%)	300KB
✅	app-drive.(hash).min.css	10.73KB (+23B +0.21%)	56KB

Unchanged files (12)

Status	Path	Size	Limits
✅	public/pdf.worker.entry.(hash).worker.js	345.35KB	350KB
✅	public/cozy-client-js.js	159.28KB	160KB
✅	intents/drive.(hash).js	87.62KB	190KB
✅	public/drive.(hash).min.css	39.93KB	100KB
✅	onlyOffice/slide.pptx	24.83KB	25KB
✅	intents-drive.(hash).min.css	7.89KB	40KB
✅	onlyOffice/text.docx	5.85KB	6KB
✅	onlyOffice/spreadsheet.xlsx	5.02KB	6KB
✅	manifest.webapp	1.87KB	2KB
✅	index.html	598B	1KB
✅	intents/index.html	507B	1KB
✅	manifest.json	185B	1KB

Total files change +5.54KB +0.11%

Groups updated (4)

Status	Path	Size	Limits
✅	services/**	545.23KB (+2.57KB +0.47%)	-
✅	public/**	2.11MB (+1.56KB +0.07%)	-
✅	vendors/**	1.79MB (+1.31KB +0.07%)	-
✅	app/**	161.61KB (+80B +0.05%)	-

Unchanged groups (3)

Status	Path	Size	Limits
✅	intents/**	88.12KB	-
✅	onlyOffice/**	35.7KB	-
✅	img/**	5.85KB	-

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[Merkur39]

👍

[Merkur39]

nit: Ca pourrait sans doute être mémo sur isMobile pour éviter les multiples créations

[cballevre]

Je dirais qu'il y a pas besoin car le temps de calcul de gutters n'est pas assez élever pour que ça soit pertinent et le composant n'est pas re-rendu car les paramètres ne change pas durant le rendu

[Merkur39]

Suggested change

	componentsProps: {}
	componentsProps: {
	sharedBadge: {}
	}

Ce qui permettrai d'éviter la condition componentsProps.sharedBadge ?? {} plus haut ?