fixes #1698 - Update PropertyValues Id type to string

[jbyt1]

fixes 1698 - Update PropertyValues Id type to string to avoid GUID parse exception when getting property bags containing ID field.

[jbyt1]

This solves the parsing issue in #1698
But it doesn't guarantee the Id property in the PropertyValues model will be unique if the user has configured an Id file property which can be any value.

Is uniqueness for the model's key field a requirement?
If so, any suggestions on what the preferred fix would be for this?

[Adam-it]

@jbyt1, thanks for looking into it and sorry for the late update.
I feel like this PR is more fixing the outcome with a workaround instead of addressing the conflict naming problem and as a result, we will lose type safety.
I will set this PR to draft for now and on the related issue lets first agree on the best fix for this problem