feat(ui): show access management tab for containers

[taakurof]

We use the Access Management feature of Datahub in our organisation and saw that this aspect is not currently supported for Containers. This PR aims to change that.

Checkist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[codecov]

Bundle Report

Changes will decrease total bundle size by 70.72kB (-0.32%) ⬇️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
datahub-react-web-esm	22.16MB	-70.72kB (-0.32%) ⬇️

Affected Assets, Files, and Routes:

view changes for bundle: datahub-react-web-esm

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
assets/index-*.js	-70.72kB	18.53MB	-0.38%

Files in assets/index-*.js:

• ./src/app/entityV2/container/ContainerEntity.tsx → Total Size: 6.99kB

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[asikowitz]

Thanks for the contribution! High-level this makes sense, I just have a couple questions / requests

[asikowitz]

In the v1 ContainerEntity, we have:

                        enabled: (_, container: GetContainerQuery) => {
                            const accessAspect = container?.container?.access;
                            const rolesList = accessAspect?.roles;
                            return !!accessAspect && !!rolesList && rolesList.length > 0;
                        },

Did you omit this for a specific reason?

[taakurof]

Thanks for the quick response!
I omitted this from ContainerEntity, to be consistent with DatasetEntity which too dropped the rules when going from entity to entityV2. This might make it clearer and more consistent for the user instead of the tab not being enabled for one entity type, but enabled for other.
There might have been additional reasoning - I will consult with my colleague.

[asikowitz]

Suggested change

	name: 'Access Management',
	name: 'Access',

For consistency with the rest of the platform

[taakurof]

Hey 👋 Yup, changed this.

[asikowitz]

Makes sense to me, thanks for your contribution!