[UX] Incomplete process path copy

As you can see in the screenshot in the first and second process before /bin/d3ddriveruery64.exe the path is broken. In the third process the path is broken at the end.

I can't comment on Case 1 and Case 2, but regarding Case 3, I notice that command line paths seem to be cut off after 1023 characters. This also affects the tooltip for the process. I can reproduce this case with the Flatpak version of Microsoft Teams. For a specific rendering process that's currently running:

Output from Task Manager:

/app/extra/teams/teams --type=renderer --autoplay-policy=no-user-gesture-required --disable-background-timer-throttling --field-trial-handle=13069095695697807755,14411470483607476991,131072 --enable-features=ContextBridgeMutability,WebComponentsV0Enabled --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --lang=en-US --enable-crash-reporter=3b402e79-41dd-4a63-88b0-fa82a6335f57,no_channel --global-crash-keys=3b402e79-41dd-4a63-88b0-fa82a6335f57,no_channel,_companyName=Microsoft,_productName=com.microsoft.teams.linux,_version=1.4.00.26453 --ms-teams-less-cors=522133263 --app-path=/app/extra/teams/resources/app.asar --no-sandbox --no-zygote --preload=/app/extra/teams/resources/app.asar/lib/pluginhost/preload.js --context-isolation --background-color=#fff --enable-spellcheck --enable-websql --disable-electron-site-instance-overrides --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=13 --no-v8-untrusted-code-mitigations --s

Output from ps -eo args:

/app/extra/teams/teams --type=renderer --autoplay-policy=no-user-gesture-required --disable-background-timer-throttling --field-trial-handle=13069095695697807755,14411470483607476991,131072 --enable-features=ContextBridgeMutability,WebComponentsV0Enabled --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --lang=en-US --enable-crash-reporter=3b402e79-41dd-4a63-88b0-fa82a6335f57,no_channel --global-crash-keys=3b402e79-41dd-4a63-88b0-fa82a6335f57,no_channel,_companyName=Microsoft,_productName=com.microsoft.teams.linux,_version=1.4.00.26453 --ms-teams-less-cors=522133263 --app-path=/app/extra/teams/resources/app.asar --no-sandbox --no-zygote --preload=/app/extra/teams/resources/app.asar/lib/pluginhost/preload.js --context-isolation --background-color=#fff --enable-spellcheck --enable-websql --disable-electron-site-instance-overrides --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=13 --no-v8-untrusted-code-mitigations --shared-files=v8_snapshot_data:100 --msteams-process-type=pluginHost

Based on my initial investigation, it looks like this issue might be coming from https://gitlab.xfce.org/apps/xfce4-taskmanager/-/blob/58cf9b2694d539a4066517a7e2ac88587b1b5937/src/task-manager.h#L31 which causes https://gitlab.xfce.org/apps/xfce4-taskmanager/-/blob/58cf9b2694d539a4066517a7e2ac88587b1b5937/src/task-manager-linux.c#L149 to get at most 1024 - 1 = 1023 characters. I have not looked into the other task-manager-(system).c files yet to verify if they are doing similar things, but I would assume so since Task->cmdline only has room for 1024 chars.

Please update the software version tag after raising the limit, as this is quite an important update and the version has not been updated for a year. (useful for distributions which update by version rather than git slices)