Force sync registrations on --force-events flag

[sangeetha5491]

Description

The PR contains the following changes:

Since aio app use is a pre-requisite for deploying registrations and may not always be executed by the user, this PR removes this dependency by making a call to IO events to always fetch the registrations in the workspace before updating them.

--force-events flag if true, will result in deletion of registrations that are part of the app.config.yaml file but not part of the Console workspace.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

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 change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov]

Codecov Report

Merging #64 (e89ca41) into master (b63559b) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #64   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           24        24           
  Lines          596       611   +15     
  Branches        82        82           
=========================================
+ Hits           596       611   +15     

Impacted Files	Coverage Δ
src/hooks/post-deploy-event-reg.js	100.00% <100.00%> (ø)
src/hooks/utils/hook-utils.js	100.00% <100.00%> (ø)
test/mocks.js	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[moritzraho]

Looks good to me, makes sense to use the events API directly.