Editing Shared Resource Specs Limited by Invoker's Usage

**Description:**
Currently, when attempting to edit the specifications of a shared resource owned by another user, the action is restricted based on the invoker's usage limits. This behavior may cause unexpected limitations when administrative users or automation processes need to modify shared resources.

**Steps to Reproduce:**

A user creates a shared resource.
Another user with 100% usage (or `quota` - `usage` < `modified amount` ) in the team attempts to modify the resource specs.
The modification is blocked in the frontend due to the invoker's own usage limits.

**Expected Behavior:**

Users in the team should be able to modify shared resource specs without being constrained by their own usage limits.
It should be constrained by the owners usage.

**Actual Behavior:**

Editing is prevented if the invoker exceeds their usage limits, even if the resource belongs to another user.

This is a frontend bug caused by how the resources left are calculated in the `Specs.tsx` it currently calculates based on the user, it should instead calculate based on the owner. Maybe omit this frontend limit for shared resources since it is handled by the backend and a user that is not admin cannot and should not be able to see other users usages.

Open Specs.tsx and trace how the remaining resources are calculated for shared-resource edits. Reproduce the case where the invoker has no available usage but the owner does, then verify that editing is no longer blocked by the invoker's limits while the owner's limits remain authoritative.

Written by the indexing model from the issue text.