prevent conflict between status bar item ids

[CGNonofr]

fix #201795

instead of using a incremented id which can conflict between extHosts, use an uuid which will always be unique

[bpasero]

We seem to be using 2 identifiers for the status bar entry, the one I added later was for allowing to show/hide entries and does not seem to be impacted by this change. The one that is impacted here however is a different identifier that was already there from before (entryId) and I am not entirely sure if that can just work with UUIDs, adding Jo to look at it as well.

[jrieken]

instead of using a incremented id which can conflict between extHosts, use an uuid which will always be unique

This is an interesting find and there is something do but just using a UUID will introduce other bugs. The setStatusBarMessage-API uses a status bar item with incrementing id and for that it is actually wanted to be reused across EHs. All other items have an associated extension identifier so we might simply wanna use a default id