UI improvements to DTL Editor

I'd like several improvements to the DTL editor

1. I'd like to have a visual clue to know if a property is marked as required, both in the source object and the targer object. If a property is required in the target object I would like to know that I need to ensure that it gets set in some way.

2. I'd like to know if a property is marked as [Deprecated] in a visual way. A number of properties in HS.SDA3.* have been marked as deprecated but there's now visual clue in the DTL editor that you likely dont want to set them

3. It's not super obvious in the list of properties for the source and target what the sort order is. It doesnt look like its alphabetical, it might be based on SQLColumn number when the object is a persistent class but with really large classes you spend a lot of time scrolling up and down trying to find a property you know exists, you just dont know where it is in the object.

4. I'd like to be able to see the datatype of a property. Sometimes a property might be called BirhtDate and it might be defined as a %TimeStamp. Without know the data type its not immediately clear of you have to wrap the setting with a conversion function. Another reason to know the data type is sometimes you "think" the field is a %String but in fact it is based off of HS.SDA3.CodeTableDetail. As such you wouldn't want to set target.Address.City="Boston" but rather would need to set target.Address.City.Description="Boston"

5. I'd like to see the Valuelist of a property. If there is a constraint on a property such that it only accepts a finite list of values I'd like to be able to see that.

6. When using a DTL that has a source that is based on a recordmap I'd like some way to mark a property on the source to be hidden so as to make the record map simpler to view. Once I've decided I have no place to map a field from the source to the target, I'd like to get it out of my immediate view.

7. I'd like to be able to see the description of a property in the class for the source or target. When mapping RecordMap data to HS.SDA3.* there plenty of good property descriptions that provide context about the property I'm setting.

Some of this was reported in DP-413080