fix(jenkins-backend): use same config prop name

Signed-off-by: TANGUY Antoine (SIB) <tanguyantoine@users.noreply.github.com>

.changeset/quiet-hats-kick.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-jenkins-backend': patch
+---
+
+fix incorrect jenkins backend config initialization. named config and non named config use extraRequestHeaders

plugins/jenkins-backend/src/service/jenkinsInfoProvider.test.ts

@@ -55,7 +55,7 @@ describe('JenkinsConfig', () => {
               baseUrl: 'https://jenkins.example.com',
               username: 'backstage - bot',
               apiKey: '123456789abcdef0123456789abcedf012',
-              headers: {
+              extraRequestHeaders: {
                 myHeader: 'my-value',
               },
             },
@@ -70,7 +70,7 @@ describe('JenkinsConfig', () => {
         baseUrl: 'https://jenkins.example.com',
         username: 'backstage - bot',
         apiKey: '123456789abcdef0123456789abcedf012',
-        headers: {
+        extraRequestHeaders: {
           myHeader: 'my-value',
         },
       },

plugins/jenkins-backend/src/service/jenkinsInfoProvider.ts

@@ -84,7 +84,7 @@ export class JenkinsConfig {
         baseUrl: c.getString('baseUrl'),
         username: c.getString('username'),
         apiKey: c.getString('apiKey'),
-        headers: c.getOptional('headers'),
+        extraRequestHeaders: c.getOptional('extraRequestHeaders'),
         crumbIssuer: c.getOptionalBoolean('crumbIssuer'),
       })) || [];