Update convert to record rules for conversion

- update rules to allow for override of equals(), hashCode()
  and toString() methods

Author: jjohnstn

news/4.39/jdt.md

@@ -69,8 +69,9 @@ Javadoc pop‑up shown after activating the proposal
 A new refactoring has been added: `Right-click` -> `Refactoring` -> `Convert Class to Record...`, which will convert an appropriate class into a record.
 
 1. The class must have only one or more private instance field members that are all initialized in a single constructor by simple assignment and no static members.
-2. The class must have at most one getter method per instance field that simply returns the field value and no other methods.
+2. The class must have at most one getter method per instance field that simply returns the field value.
 3. The class can only extend Object and cannot implement any interface.
+4. The class may override `equals()`, `hashCode()`, or `toString()` from Object and these will be copied into the record but it cannot have any other methods except for the aforementioned constructor and getter methods.
 
 The refactoring may note that the conversion is not possible or issue a warning before conversion:
 for example, if there is a field that does not have a getter, a warning will be issued that the field will be exposed via an accessor and the user may choose to continue or not.