Lock down bucket management to proper permissions

[kamorel]

Description

Ensures user has proper rights and permissions to action certain bucket management functionality.

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

• I have read the CONTRIBUTING doc
• I have checked that unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[github-actions]

Coverage Report (Application)

Totals
Statements:	75% ( 51 / 68 )
Methods:	62.5% ( 5 / 8 )
Lines:	82.61% ( 38 / 46 )
Branches:	57.14% ( 8 / 14 )

[github-actions]

Coverage Report (Frontend)

Totals
Statements:	5.42% ( 42 / 775 )
Methods:	0% ( 0 / 180 )
Lines:	8.39% ( 40 / 477 )
Branches:	1.69% ( 2 / 118 )

[jujaga]

Logically makes sense. We should make a general consistency pass on action naming conventions though to avoid naming things as get* when they aren't computed types.

[jujaga]

Should we be declaring and destructuring this in advance on setup function instead? It might end up helping this specific .js bundle be smaller in size if we only imported that one function instead of the entire permission store's methods.

<script setup lang="ts">
import { useAuthStore, useBucketStore, usePermissionStore } from '@/store';
const { isUserElevatedRights } = usePermissionStore();
</script>

<Button v-if="isUserElevatedRights()" >

Granted, this does contrast with our previous conversations about store readability (which store am I invoking from?)