feat: use TF API to detect TF scope from API key

`tf_scope` input is now deprecated and will be removed in the future.
The value of `tf_scope` is now ignored and whoami API endpoint is used to detect the scope.

Fixes #315

Author: jamacku

README.md

@@ -29,7 +29,7 @@ See [Testing Farm onboarding guide](https://docs.testing-farm.io/Testing%20Farm/
 |------------|-------------|---------------|
 | `api_key`  | Testing farm API key | empty, **required from user** |
 | `api_url`  | Testing farm API server url | https://api.dev.testing-farm.io/v0.1 |
-| `tf_scope` | Define the scope of Testing Farm. Possible options are 'public' or 'private' | public |
+| `tf_scope` | **Deprecated**, this input is no longer used. `tf_scope` is now automatically detected based on the provided `api_key`. ~Define the scope of Testing Farm. Possible options are 'public' or 'private'~ | public |
 
 ### Tmt Metadata
 

action.yml

@@ -16,6 +16,7 @@ inputs:
   tf_scope:
     description: 'Defines the scope of Testing Farm. Possible options are public and private'
     required: false
+    deprecationMessage: 'This input is no longer used. tf_scope is now automatically detected based on the provided api_key. Will be removed in the future.'
     default: 'public'
 
   # Tmt Metadata

dist/action.js

@@ -36,7 +36,7 @@
     "@octokit/types": "16.0.0",
     "date-fns": "4.1.0",
     "issue-metadata": "0.2.4",
-    "testing-farm": "1.11.0",
+    "testing-farm": "1.12.0",
     "zod": "4.1.12"
   },
   "devDependencies": {