Refactor TargetUnit queries for consistency

- Renamed `getTargetUnitsQuery` to `TARGET_UNITS_QUERY` for improved clarity and consistency in naming conventions.
- Updated the import statement in `TargetUnitRepository` to reflect the new query name.

These changes enhance code readability and maintainability within the TargetUnit service.

Author: anatolyshipitz

workers/main/src/services/TargetUnit/TargetUnitRepository.ts

@@ -3,7 +3,7 @@ import { Pool } from 'mysql2/promise';
 import { TargetUnitRepositoryError } from '../../common/errors';
 import { GroupName, TargetUnit } from '../../common/types';
 import { ITargetUnitRepository } from './ITargetUnitRepository';
-import { getTargetUnitsQuery } from './queries';
+import { TARGET_UNITS_QUERY } from './queries';
 import { TargetUnitRow } from './types';
 
 export class TargetUnitRepository implements ITargetUnitRepository {
@@ -36,7 +36,7 @@ export class TargetUnitRepository implements ITargetUnitRepository {
   async getTargetUnits(groupName: GroupName): Promise<TargetUnit[]> {
     try {
       const [rows] = await this.pool.query<TargetUnitRow[]>(
-        getTargetUnitsQuery,
+        TARGET_UNITS_QUERY,
         [groupName],
       );
 

workers/main/src/services/TargetUnit/queries.ts

@@ -1,4 +1,4 @@
-export const getTargetUnitsQuery = `SELECT
+export const TARGET_UNITS_QUERY = `SELECT
     group_id,
     group_name,
     project_id,