RC2: Fix missing force delete when keep === 0 bug

The comparison to check if the force parameter should be supplied the string based input argument and not the parsed number when comparing with the number 0. Thus force would always be false, even for those cases where keep === 0. This is now fixed.

Release candidate with deployment trigger type filtering support

This release adds support for filtering (or not) on the Cloudflare deployment trigger types using the deployment_trigger input. This allows deletion of deployments using the ad_hoc trigger type. Additionally the release now supports an optional keep input. This defaults to 0, but you can optionally specify a number of deployments to keep.

The deployment trigger type support was contributed by @zaosoula. Thanks ❤️

Initial Cloudflare Deployments deletion action

Cloudflare Delete Deployments implements a JavaScript GitHub Action that helps you clean up Cloudflare Deployments. It supports specifying the branch (i.e., deployment alias) and since date time for which to delete deployments. The action is beneficial when you want to delete all but the last deployment for a pull request or branch.

This release is tested internally for Adventure Tech but should be considered alpha.