Support administrative_contact and technical_contact in the Console

[ryaplots]

Summary

Closes #6112

Changes

• Add contacts to relevant entities.

Screenshots

Testing

Manually

Notes for Reviewers

I decided to add this in the entity general settings, as this is the place where I have access to the collaborator's rights for the entity, and not in the user settings as we initially thought.

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

[kschiffer]

I think we'll have to rework the UX here a bit. See also my comment here:
#6112 (comment)

I'll look into this later this week/next week. Should not affect the implementation as a whole too much though.

[kschiffer]

Currently blocked, so reopening once #6112 is merged.

[ryaplots]

This is unblocked.

[adriansmares]

Does this take in account that in certain deployments collaborators can set only themselves as contacts, but not others (#6378) ?

[ryaplots]

Does this take in account that in certain deployments collaborators can set only themselves as contacts, but not others (#6378) ?

Should we inform those users of that, with a notification? @kschiffer

[kschiffer]

As far as I understand, we can determine this based on the IS configration fetched from the backend. If indeed the user fan only set itself, the console should deactivate the selector field and render a button 'Set yourself as contact' to the fields. Clicking the button will then put the user into the field.

There should also be a notification above the field saying:

You can only set yourself as a contact. If you would like another collaborator set as contact, please contact this collaborator to self-assign as contact.

[kschiffer]

EDIT: Disregard; didn't pull latest changes.

[kschiffer]

diff --git a/pkg/webui/lib/store/selectors/collaborators.js b/pkg/webui/lib/store/selectors/collaborators.js
index 8293e4f83..940b6f468 100644
--- a/pkg/webui/lib/store/selectors/collaborators.js
+++ b/pkg/webui/lib/store/selectors/collaborators.js
@@ -12,6 +12,8 @@
 // See the License for the specific language governing permissions and
 // limitations under the License.
 
+import { createSelector } from 'reselect'
+
 import { createFetchingSelector } from '@ttn-lw/lib/store/selectors/fetching'
 import { createErrorSelector } from '@ttn-lw/lib/store/selectors/error'
 import {
@@ -59,8 +61,10 @@ const createSelectCollaboratorsFetchingSelector = createFetchingSelector(
 )
 const createSelectCollaboratorsErrorSelector = createErrorSelector(GET_COLLABORATORS_LIST_BASE)
 
-export const selectCollaborators = state =>
-  createSelectCollaboratorsIdsSelector(state).map(id => selectCollaboratorById(state, id))
+export const selectCollaborators = createSelector(
+  [createSelectCollaboratorsIdsSelector, selectCollaboratorsEntitiesStore],
+  (collaboratorIds, collaborators) => collaboratorIds.map(id => collaborators[id]),
+)
 export const selectCollaboratorsTotalCount = state =>
   createSelectCollaboratorsTotalCountSelector(state)
 export const selectCollaboratorsFetching = state => createSelectCollaboratorsFetchingSelector(state)

Please also apply this change to remove the warning in the Console, and please make sure to not ignore warnings: