Generic lookup of files and flags

[jonesbusy]

Make metadata more generic. In order to have more information about the presence or not of file and activate some recipes or not depending on conditions

Sorry @sridamul but we will get some conflict on #201 I let you choose which on we merge first

Testing done

Automated tests. An checking a plugin contains following data

{
  "pluginName": "ASM API Plugin",
  "flags": [
    "SCM_HTTPS",
    "MAVEN_REPOSITORIES_HTTPS"
  ],
  "commonFiles": [
    "POM",
    "JENKINSFILE"
  ],
  "otherFiles": [
    "src/main/resources/index.jelly",
    "src/test/java/io/jenkins/plugins/asm/ASMSmokeTest.java",
    ".mvn/extensions.xml",
    ".github/dependabot.yml",
    ".github/workflows/cd.yaml",
    ".github/workflows/jenkins-security-scan.yml",
    ".github/CODEOWNERS",
    ".mvn/maven.config",
    "README.md",
    "LICENSE.md",
    ".gitignore"
  ],
  "jenkinsVersion": "2.440.3",
  "parentVersion": "4.86",
  "properties": {
    "revision": "9.7",
    "changelist": "999999-SNAPSHOT",
    "jenkins.baseline": "2.440",
    "jenkins.version": "${jenkins.baseline}.3",
    "gitHubRepo": "jenkinsci/${project.artifactId}-plugin",
    "spotless.check.skip": "false"
  },
  "key": "plugin-metadata",
  "path": "asm-api"
}

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[jonesbusy]

@sridamul Will be perfect to merge our 2 PRs ;)

[sridamul]

Great Idea! Thank you very much.

[sridamul]

We can merge this, I will fix other conflicts on #201

[jonesbusy]

Thanks, I will not touch the visitors (only add more Flags and CommonFile which are not extracted and should not cause conflicts