(feature): remove integration router and use catalog resource type since we use the same resources required by the catalog entity

Signed-off-by: Hasan Oezdemir <21654050+nodify-at@users.noreply.github.com>

plugins/jenkins-common/api-report.md

@@ -8,8 +8,5 @@ import { Permission } from '@backstage/plugin-permission-common';
 // @public
 export const jenkinsExecutePermission: Permission;
 
-// @public (undocumented)
-export const RESOURCE_TYPE_JENKINS = 'jenkins';
-
 // (No @packageDocumentation comment for this package)
 ```

plugins/jenkins-common/package.json

@@ -22,6 +22,7 @@
     "clean": "backstage-cli package clean"
   },
   "dependencies": {
+    "@backstage/plugin-catalog-common": "^0.1.4",
     "@backstage/plugin-permission-common": "^0.5.1"
   },
   "devDependencies": {

plugins/jenkins-common/src/permissions.ts

@@ -13,13 +13,9 @@
  * See the License for the specific language governing permissions and
  * limitations under the License.
  */
+import { RESOURCE_TYPE_CATALOG_ENTITY } from '@backstage/plugin-catalog-common';
 import { Permission } from '@backstage/plugin-permission-common';
 
-/**
- * @public
- */
-export const RESOURCE_TYPE_JENKINS = 'jenkins';
-
 /**
  * This permission is used to determine if a user is allowed to execute an action in jenkins plugin
  *
@@ -30,5 +26,5 @@ export const jenkinsExecutePermission: Permission = {
   attributes: {
     action: 'update',
   },
-  resourceType: RESOURCE_TYPE_JENKINS,
+  resourceType: RESOURCE_TYPE_CATALOG_ENTITY,
 };