Cache if package maintainer is an author of the package to avoid multiple API calls

[zeusongit]

Purpose

https://jira.autodesk.com/browse/DYN-5103

When a user right clicks a package in Dynamo package manager preference tab, we check if the user is an author of that package or not in order to enable/disable Deprecate/Undeprecate option for that package.

Created a cache in Dynamo to record the result so that we do not call the API again and again for one session.

Declarations

Check these if you believe they are true

• The codebase is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.
• This PR modifies some build requirements and the readme is updated

Release Notes

Created a cache in Dynamo to record the result so that we do not call the API again and again for one session.

Reviewers

@QilongTang

[mjkkirschner]

do we check this again / refresh if the user logs out / logs in as another user?

[zeusongit]

do we check this again / refresh if the user logs out / logs in as another user?

Not tested that scenario in revit, but it will break in that case, as Dictionary will have stale values.
Can user remain in Dynamo and logout? Because if it needs a restart then this could work.
I will test this and update.

[zeusongit]

I checked in Revit, we cannot sign out without quitting, not sure about other integrators. @mjkkirschner

.

[QilongTang]

LGTM does it make sense to add a unit test for this update?

[zeusongit]

LGTM does it make sense to add a unit test for this update?

Unit test is not helpful, as we call the parent method for result, internally it uses cached or API response, with no way of knowing the difference.