feat(FR-826): allow role setting when creating a new user (#3491)

Resolves #3490 ([FR-826](https://lablup.atlassian.net/browse/FR-826))

# Refactor form handling in FolderCreateModal and fix UserSettingModal role check

This PR makes two improvements:

1. In `FolderCreateModal.tsx`, simplifies the mutation function by using the spread operator to pass form values instead of explicitly listing each field.

2. In `UserSettingModal.tsx`, fixes a potential bug by removing an unnecessary check for `user?.role` when determining whether to display the role selection dropdown. The condition now only depends on `currentUserRole` being defined and having appropriate permissions.

**Checklist:**

- [ ] Documentation
- [ ] Minium required manager version
- [ ] Specific setting for review (eg., KB link, endpoint or how to setup)
- [ ] Minimum requirements to check during review
- [ ] Test case(s) to demonstrate the difference of before/after

[FR-826]: https://lablup.atlassian.net/browse/FR-826?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

Author: agatha197

react/src/components/FolderCreateModal.tsx

@@ -115,11 +115,7 @@ const FolderCreateModal: React.FC<FolderCreateModalProps> = ({
   >({
     mutationFn: (values) => {
       const body = {
-        name: values.name,
-        host: values.host,
-        group: values.group,
-        usage_mode: values.usage_mode,
-        permission: values.permission,
+        ...values,
         cloneable: values.cloneable ?? false,
       };
       return baiRequestWithPromise({

react/src/components/UserSettingModal.tsx

@@ -427,8 +427,7 @@ const UserSettingModal: React.FC<UserSettingModalProps> = ({
             })}
           />
         </Form.Item>
-        {!!user?.role &&
-          !!currentUserRole &&
+        {!!currentUserRole &&
           currentUserRole in permissionRangeOfRoleChanges && (
             <Form.Item name="role" label={t('credential.Role')}>
               <Select