chore: Set release-please project type

[jsonbailey]

No description provided.

[semgrep-code-launchdarkly]

Semgrep identified an issue in your code:
An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.

To resolve this comment:

✨ Commit Assistant fix suggestion

Suggested change

	- uses: googleapis/release-please-action@v4
	# Pinned to release-please-action v4.1.3 (latest v4 as of 2024-06-19) full commit SHA for security.
	- uses: googleapis/release-please-action@e4a25f5d3b35603cdb70b79679d3f42b8415fafe

View step-by-step instructions

1. Go to the official googleapis/release-please-action GitHub repository and find the latest commit SHA for the v4 branch or tag: https://github.com/googleapis/release-please-action/commits/v4
2. Copy the full 40-character commit SHA for the latest desired release.
3. Update the uses: line from googleapis/release-please-action@v4 to googleapis/release-please-action@<full-commit-sha>, replacing <full-commit-sha> with the value you copied.
   For example: uses: googleapis/release-please-action@e4a25f5d3b35603cdb70b79679d3f42b8415fafe
4. Save your changes.

Pinning actions to a full commit SHA ensures that your workflow will always use exactly the same version of the action code, even if the branch or release tag is moved or changed later.

💬 Ignore this finding

Reply with Semgrep commands to ignore this finding.

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by third-party-action-not-pinned-to-commit-sha.

_{You can view more details about this finding in the Semgrep AppSec Platform.}