refactor(dto): clean up unused import in MaxByteLength

Author: gpascucci

backend/src/main/java/ca/bc/gov/nrs/ilcr/dto/base/MaxByteLength.java

@@ -1,6 +1,5 @@
 package ca.bc.gov.nrs.ilcr.dto.base;
 
-import ca.bc.gov.nrs.ilcr.exception.ScheduleNotSavedException;
 import jakarta.validation.Constraint;
 import jakarta.validation.Payload;
 import java.lang.annotation.Documented;
@@ -18,8 +17,8 @@
  * {@code ALL_TAB_COLUMNS} reports {@code CHAR_USED = 'B'} for {@code CAMP_REPORT.CAMP_NAME} (30)
  * and {@code CAMP_REPORT.COMMENTS} (4000). {@code @Size} measures Java characters, so a name of 30
  * accented or CJK characters satisfies it and then overflows a 30-BYTE column: Oracle raises
- * ORA-12899, the service can only map that {@code DataAccessException} to {@code
- * ScheduleNotSavedException}, and the licensee gets an opaque 500 on an ordinary save. This
+ * ORA-12899, the service can only map that {@code DataAccessException} to {@link
+ * ca.bc.gov.nrs.ilcr.exception.ScheduleNotSavedException ScheduleNotSavedException}, and the licensee gets an opaque 500 on an ordinary save. This
  * constraint turns that into a clean 400 at the same field. The character cap stays because it is
  * the LEGACY bound (the screen's own {@code maxlength}) and is the tighter one for ASCII input,
  * which is effectively all stored data today.