refactor: simplify workflow skip logic using do_not_skip parameter (#114)

* feat: ensure workflows never skip execution during version releases

- Modified skip-duplicate-actions to never skip when pushing tags
- Updated all workflow jobs to force execution for tag pushes (version releases)
- Ensures complete CI/CD pipeline execution for releases including:
  - All tests and lint checks
  - Multi-platform builds
  - GUI builds
  - Release asset creation
  - OSS uploads

This guarantees that version releases always undergo full validation
and build processes, maintaining release quality and consistency.

* refactor: simplify workflow skip logic using do_not_skip parameter

- Replace complex conditional expressions with do_not_skip: ['release', 'push']
- Add skip-duplicate-actions to docker.yml workflow
- Ensure all workflows use consistent skip mechanism
- Maintain release and tag push execution guarantee
- Simplify job conditions by removing redundant tag checks

This change makes workflows more maintainable and follows
official skip-duplicate-actions best practices.

.github/workflows/build.yml

@@ -79,6 +79,8 @@ jobs:
           concurrent_skipping: "same_content_newer"
           cancel_others: true
           paths_ignore: '["*.md", ".github/**", "docs/**", "deploy/**", "scripts/dev_*.sh"]'
+          # Never skip release events and tag pushes
+          do_not_skip: '["release", "push"]'
 
   # Second layer: Business logic level checks (handling build strategy)
   build-check:
@@ -105,9 +107,11 @@ jobs:
             build_type="development"
           fi
 
+          # Always build for tag pushes (version releases)
           if [[ "${{ startsWith(github.ref, 'refs/tags/') }}" == "true" ]]; then
             should_build=true
             build_type="release"
+            echo "🏷️  Tag detected: forcing release build"
           fi
 
           echo "should_build=$should_build" >> $GITHUB_OUTPUT