ci: Auto update yarn.lock as part of release

[adchia]

What this PR does / why we need it:
There was an issue now that the release publishes new NPM packages for the UI as part of the flow. Roughly it's:

1. Semantic release bumps file versions (including ui package version) and creates a tagged commit.
2. When building the wheel, it needs to compile the Feast UI to bundle into the release. This updates the yarn.lock file because now there's a new published NPM version of the Feast UI.
3. Because now the client is dirty with local changes, the built wheel is a dev wheel instead of a clean wheel (see https://github.com/pypa/setuptools_scm/#default-versioning-scheme).

This change instead now will publish the NPM release before running semantic release:

• Find the new release with a dry run of the semantic release to get the old / new release versions (Semantic Release does not support this yet, as per Add an option to output the version that would be published semantic-release/semantic-release#753)
• Temporarily bump file versions using above versions
• Publish Web UI

Then, Semantic release will additionally run make build-ui and check in the updated yarn.lock file before tagging the release
Which issue(s) this PR fixes:

Fixes #

[kevjumba]

/lgtm

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adchia, kevjumba

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [adchia,kevjumba]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment