[YUNIKORN-2153]Optimize Placement of predicateCheckResult for Better Maintainability

[kaichiachen]

What is this PR for?

Create predicate.go to encapsulate the declaration and implementation of predicateCheckResult, improves code organization by centralizing predicate-related logic, enhancing maintainability and readability.

What type of PR is it?

• - Bug Fix
• - Improvement
• - Feature
• - Documentation
• - Hot Fix
• - Refactoring

Todos

• - Task

What is the Jira issue?

https://issues.apache.org/jira/projects/YUNIKORN/issues/YUNIKORN-2153

How should this be tested?

1. Unit test

#> go test -cover ./pkg/scheduler/objects/...                
ok      github.com/apache/yunikorn-core/pkg/scheduler/objects   (cached)        coverage: 88.9% of statements
ok      github.com/apache/yunikorn-core/pkg/scheduler/objects/events    (cached)        coverage: 100.0% of statements
ok      github.com/apache/yunikorn-core/pkg/scheduler/objects/template  (cached)        coverage: 100.0% of statements

2. Manual Preemtion test
   2.1 Create cluster with kind and install yunikorn
   2.2 Create pods with low priority but request a lot of resources
   2.3 Create a pod with higher priority
   2.4 Some of pods created at 2.2 are eviction and pod in 2.3 can be scheduled to k8s cluster

Screenshots (if appropriate)

Questions:

• - The licenses files need update.
• - There is breaking changes for older versions.
• - It needs documentation.