[Improvement] : Added disabled option to input element in RolePermissionRow.jsx

[rautniraj]

This will prevent piling of multiple POST request to update role permission api simultaneously. We will disable the button when the api is in loading state.

This makes sense mostly for the CreateRoom Permission. Because at backend, once this option is enabled not only it performs the update action but also it has chained operation of creating rooms for user. This might take some time in completion and then returning success message, if there are large chunks of users for whom this needs to be done. So consecutive request needs to be handled well.

def create_default_room
	return unless role_params[:name] == 'CreateRoom' && role_params[:value] == true
        User.includes(:rooms)
              .with_provider(current_provider)
              .where(role_id: role_params[:role_id])
              .where(rooms: { id: nil }).find_in_batches do |group|
            group.each do |user|
              Room.create(name: t('room.new_room_name', username: user.name, locale: user.language), user_id: user.id)
            end
          end
  end

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rautniraj]

We dont need this disabled option on other settings like role name, recording visibility, room limit

To make this more robust if u feel i will add them as per ur suggestion. Other than these 3, every setting is now equipped with disabled.