feat: Show number of new sharing in the sidebar

[cballevre]

### ✨ Features

* Show number of new sharing in the sidebar

On desktop :

On tablet & mobile :

[bundlemon]

BundleMon

Files updated (3)

Status	Path	Size	Limits
✅	drive/app/drive.(hash).js	243.61KB (+830B +0.33%)	255KB
✅	drive/public/drive.(hash).js	1.5MB (+499B +0.03%)	1.65MB
✅	drive/intents/drive.(hash).js	148.95KB (+486B +0.32%)	171KB

Unchanged files (16)

Status	Path	Size	Limits
✅	drive/vendors/drive.(hash).js	1.28MB	1.6MB
✅	drive/public/pdf.worker.entry.(hash).worker.j s	343.37KB	345KB
✅	drive/services/dacc/drive.js	253.91KB	500KB
✅	drive/services/qualificationMigration/drive.j s	248.95KB	500KB
✅	drive/public/cozy-client-js.js	158.97KB	160KB
✅	drive/public/drive.(hash).min.css	93.36KB	100KB
✅	drive/app-drive.(hash).min.css	55.99KB	56KB
✅	drive/intents-drive.(hash).min.css	37.07KB	40KB
✅	drive/onlyOffice/slide.pptx	24.82KB	25KB
✅	drive/onlyOffice/text.docx	5.84KB	6KB
✅	drive/onlyOffice/spreadsheet.xlsx	5.01KB	6KB
✅	drive/manifest.webapp	1.77KB	2KB
✅	drive/index.html	531B	1KB
✅	drive/intents/index.html	517B	1KB
✅	drive/img/app-icon.(hash).svg	419B	1KB
✅	drive/manifest.json	184B	1KB

Total files change +1.77KB +0.04%

Groups updated (3)

Status	Path	Size	Limits
✅	drive/app/**	243.61KB (+830B +0.33%)	+1%
✅	drive/public/**	2.09MB (+499B +0.02%)	+7%
✅	drive/intents/**	149.45KB (+485B +0.32%)	+6%

Unchanged groups (5)

Status	Path	Size	Limits
✅	drive/screenshots/**	2.13MB	+0.4%
✅	drive/vendors/**	1.28MB	+6%
✅	drive/services/**	502.86KB	+1%
✅	drive/onlyOffice/**	35.68KB	+0.4%
✅	drive/img/**	419B	+0.4%

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[Crash--]

I think we should invert the both fields. class is less restrictive than metatada.sharing.status and to have better performance we should always put first in the index the more restrictive field.

[Crash--]

as should be "technically named" not "functionally named". Because the name is used to reuse a request, it's easier to reuse the same request if the name is technical instead of functional.

See https://github.com/cozy/cozy-guidelines/#naming-of-queries

Here something like: io.cozy.files/metadata.sharing.status/new/class/shortcut