chore(workflow): use release please action

[JAdshead]

Description

This Pr replaces semantic release with release-please.

release-please will create release PR on merge to main. It will ensure that the pr is kept up to date when additional branches are merged. When a release is desired the release PR just needs to be merged.

similar to semantic release please uses conventional commits to generate release notes and determine the version.

Motivation and Context

Semantic release is best used for a workflow where releases are created on merge to main. This has friction with how GH manages branch permissions.

How Has This Been Tested?

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• My changes are in sync with the code style of this project.
• There aren't any other open Pull Requests for the same issue/update.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• This change impacts caching for client browsers.
• This change adds additional environment variable requirements for vitruvius users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using vitruvius?