HEI: Allow RDBMS Database Naming Convention that contains dash or hypen character

Currently, HEI Job or Activity does not permit the use of dash or hyphen characters in RDBMS database names (e.g., MS SQL, MySQL). While we recognize that industry naming best practices (see below) recommend avoiding them, allowing these special characters would significantly improve usability.

• PascalCase (e.g., CustomerOrder) or snake_case (e.g., customer_order) are the two industry-standard choices. Avoid combining them within the same database environment.

• UPPERCASE should be reserved strictly for native T-SQL keywords (e.g., SELECT, INSERT, WHERE, JOIN) to instantly distinguish native syntax from your database objects.

• Avoid Special Characters and Spaces: Do not use dashes (-), spaces, or punctuation. Stick to letters, numbers, and underscores.

• Never use reserved keywords (such as User, Order, Table, Date, or Name) as object names to eliminate syntactic confusion and avoid system collisions.