Change EWM license usage so more expensive tokens are only consumed on actual actions

When a user has both, an EWM Stakeholder-Token and an EWM Contributor-Token license, assigned, the Contributor license is already checked out when the user opens the EWM project area landing page.
This is caused by operations such as com.ibm.team.apt.server.exportCSV being evaluated while widgets (for example the Plans widget with “Export to CSV”) are initialized. As a result, the Contributor license is consumed even though the user only views the project dashboard and does not actually use a Contributor-only feature.

When a user has both Stakeholder and Contributor licenses assigned, and the user only performs view / navigation activities in an EWM project (for example, just opening the project area or dashboard, browsing work items, etc.), then only the Stakeholder token shall be used (or no token at all, where permitted). A Contributor token shall only be checked out when the user actually performs an operation that requires the Contributor role (e.g. Export to CSV, build-related operations, other Contributor-only actions).

In other words, we are asking that license consumption be tied to the real user action requiring the higher license, rather than to the presence of features/widgets on a page that might potentially be used.

This would align better with the documented intention that the least expensive applicable license should be used and would avoid situations where a more expensive license is consumed just because a widget with an advanced option is present on the dashboard.