Refactor workflow hold functionality to avoid relying on database to perform some checks on "user holds entityworkflow"

Simplify the logic in handling workflow on hold status by moving related checks and operations to `EntityWorkflowStep` and `EntityWorkflow` entities. This includes implementing new methods to check if a step or workflow is held by a specific user and refactoring the controller actions to use these methods.

src/Bundle/ChillMainBundle/Repository/Workflow/EntityWorkflowStepHoldRepository.php

@@ -12,7 +12,6 @@ declare(strict_types=1);
 namespace Chill\MainBundle\Repository\Workflow;
 
 use Chill\MainBundle\Entity\User;
-use Chill\MainBundle\Entity\Workflow\EntityWorkflow;
 use Chill\MainBundle\Entity\Workflow\EntityWorkflowStep;
 use Chill\MainBundle\Entity\Workflow\EntityWorkflowStepHold;
 use Doctrine\Bundle\DoctrineBundle\Repository\ServiceEntityRepository;
@@ -58,23 +57,6 @@ class EntityWorkflowStepHoldRepository extends ServiceEntityRepository
         return $this->findBy(['step' => $step]);
     }
 
-    /**
-     * @throws NonUniqueResultException
-     */
-    public function findByWorkflow(EntityWorkflow $workflow): ?EntityWorkflowStepHold
-    {
-        $qb = $this->getEntityManager()->createQueryBuilder();
-
-        $qb->select('h')
-            ->from(EntityWorkflowStepHold::class, 'h')
-            ->join('h.step', 's')
-            ->join('s.entityWorkflow', 'w')
-            ->where('w = :workflow')
-            ->setParameter('workflow', $workflow);
-
-        return $qb->getQuery()->getOneOrNullResult();
-    }
-
     /**
      * Find a single EntityWorkflowStepHold by step and user.
      *