Mono-repo updates for release

[microsoft-graph-devx-bot]

This PR contains updates from the kiota-php monorepo. Merging these changes will trigger Release-Please on this repository.

[baywet]

@Ndiritu I'm only approving one to understand the new workflow.
Who/what is supposed to create the tag here?

[Ndiritu]

@Ndiritu I'm only approving one to understand the new workflow. Who/what is supposed to create the tag here?

@baywet I initially intended for Release-Please to do the tagging, but this probably failed because the release-please-manifest version was not bumped & now conflicts with the release-as version in the release-please-config. Either way this seems like it would introduce double the number of PRs to merge across all the repos: Mono-repo updates like this one + another release please PR that triggers tagging & GH release.

I'm thinking introducing a GitHub workflow that auto-merges PRs like this & creates a tag + GH release would be more efficient.

Also considering that we'll always have to release abstractions first so that the other package's build workflows don't fail, the other package workflows can do some limited retry in installing dependencies for their auto-merge & tagging workflows to run

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud