Narrow `pr-trigger.yml` to ignore publish-only changes in workflows

After creating #169 , the build-numpy.yml workflow kicked off again despite no new version to build. This is expected due to how the existing checker workflows were designed, and the publish step wasn't going to run anyway since it wasn't on main, but it's wasteful to be running a build in this case. If it's simple enough, we should change the pr-trigger.yml workflow so that it only triggers builds when parts of the script other than the publish job are modified. This may be too complex to justify.

Alternatively, we could do some further rework (once the composite action in #169 is merged) to have it perform the publish steps in a "mock" mode, so that we're testing the publishing steps as much as possible too. It would mean letting the superfluous wheel builds to run though, without further tweaks.

pr-trigger.yml workflow から始めて build-numpy.yml と比較し、その後 #169 で導入された workflow の変更を確認します。publish-only の変更では build が開始されず、その他のスクリプトの変更では引き続き build が開始されるようにトリガー条件を更新し、結果としての workflow の動作を検証します。