[f2v] Render inline system tags using new DAV properties API

[lhsazevedo]

Ref: #39914 #37938

Summary

Display inline system tags using the new DAV properties API.

I kept the action in the files app since the previous plugin was in there as well, and I didn't found any action registration outside the files* apps. But I can move it to the systemtags app if that is preferred!

TODO

• Decide if we should move the action to the systemtags app

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[lhsazevedo]

Possible follow ups:

• Maybe we should hide the system tags (or all inline action?) on mobile to avoid truncating the node name?
  
• Looks like the search by tag feature needs to be migrated as well.

[lhsazevedo]

Done! Added some tests as well. For now I'm hiding the tags on mobile using CSS media queries, as I'm not sure if registering an size observer inside renderInline would be the proper way to make an action react to a screen resize or if we should modify the FileAction API for this instead.

Unfortunately the tags aren't being rendered on the initial DAV request after moving to the systemtags app. I checked to ensure the action is being called, and it is indeed, but looks like now the dav property isn't being registered in time for the first request. Subsequent requests have the property registered:

inline-system-tags-bug.mp4

I believe it isn't possible to register the property earlier while still in the systemtags app, is it?

[skjnldsv]

Done! Added some tests as well. For now I'm hiding the tags on mobile using CSS media queries, as I'm not sure if registering an size observer inside renderInline would be the proper way to make an action react to a screen resize or if we should modify the FileAction API for this instead.

Media queries is how it should be done.
If you wanna prevent the fetching for ressources optimisation, you can also use document.documentElement.clientWidth < 512 and not register the dav props? 🤔

Unfortunately the tags aren't being rendered on the initial DAV request after moving to the systemtags app. I checked to ensure the action is being called, and it is indeed, but looks like now the dav property isn't being registered in time for the first request. Subsequent requests have the property registered:

We actually discovered that with @juliushaertl yesterday and worked on a fix, you can ignore it :)

[lhsazevedo]

If you wanna prevent the fetching for ressources optimisation, you can also use document.documentElement.clientWidth < 512 and not register the dav props? 🤔

Not sure if the complexity trade off is worth it... We'll probably consume them in other places of the app soon, so I guess it's Ok for them to be available on mobile as well for now?