[internal] add linked issue workflow that check closing issues samples

[SudharakaP]

Resolve #24183

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[mshima]

The idea is to a have full generated sample check at closing (linked) issues at PRs. Like we have in check-issue workflow.

• the action used to get linked issues prints a warning

• the action used to get linked issues uses custom html parsing
  we should use an action that uses github's built-in closingIssuesReferences
• issues should be converted to a matrix to check every closing issue
• should generate the sample using jhipster from-issue, check frontend, backend and e2e.
• should add a summary check in case we want to make it a requirement to merge

You can use an unfinished branch https://github.com/mshima/generator-jhipster/tree/skip_ci-generate-sample that I am working in parallel to #24135.

[mshima]

@SudharakaP have you seen the workflow from the branch I´ve posted?
https://github.com/mshima/generator-jhipster/blob/skip_ci-generate-sample/.github/workflows/closing-issues-check.yml
You can use it.

[SudharakaP]

The idea is to a have full generated sample check at closing (linked) issues at PRs. Like we have in check-issue workflow.

* the action used to get linked issues prints a warning

* the action used to get linked issues uses [custom html parsing](https://github.com/go-actions/linked-issues/blob/a850d76081f69984c9f3f1d5c2f6e8d0b8743881/main.go#L14-L20)
  we should use an action that uses github's built-in [closingIssuesReferences](https://docs.github.com/en/graphql/reference/objects)

* issues should be converted to a matrix to check every closing issue

* should generate the sample using `jhipster from-issue`, check frontend, backend and e2e.

* should add a summary check in case we want to make it a requirement to merge

You can use an unfinished branch https://github.com/mshima/generator-jhipster/tree/skip_ci-generate-sample that I am working in parallel to #24135.

@mshima : I've made some changes and I believe I've addressed all the concerns here. Take a look and let me know if there's anything missing.

@SudharakaP have you seen the workflow from the branch I´ve posted? https://github.com/mshima/generator-jhipster/blob/skip_ci-generate-sample/.github/workflows/closing-issues-check.yml You can use it.

I didn't use this exactly as I found it a bit hard to understand but hope my method does the job as well. Let me know if you think there's anything I am missing and I am happy to add it. 😉

[SudharakaP]

And I've tested it with this on the current PR run;

Welcome to JHipster v8.0.0

Welcome to the JHipster Information Sub-Generator



tmp@0.0.1-SNAPSHOT /home/afcn/code/tmp
└── generator-jhipster@8.0.0



##### **JHipster configuration, a `.yo-rc.json` file generated in the root folder**


<details>
<summary>.yo-rc.json file</summary>
<pre>
{
  "generator-jhipster": {
    "applicationType": "monolith",
    "authenticationType": "jwt",
    "baseName": "appNg2",
    "buildTool": "gradle",
    "cacheProvider": "ehcache",
    "ci": true,
    "clientFramework": "angular",
    "clientPackageManager": "npm",
    "creationTimestamp": 1596513172471,
    "databaseType": "sql",
    "devDatabaseType": "postgresql",
    "enableHibernateCache": true,
    "enableTranslation": true,
    "jhiPrefix": "custom",
    "jwtSecretKey": "ZjY4MTM4YjI5YzMwZjhjYjI2OTNkNTRjMWQ5Y2Q0Y2YwOWNmZTE2NzRmYzU3NTMwM2NjOTE3MTllOTM3MWRkMzcyYTljMjVmNmQ0Y2MxOTUzODc0MDhhMTlkMDIxMzI2YzQzZDM2ZDE3MmQ3NjVkODk3OTVmYzljYTQyZDNmMTQ=",
    "languages": ["en"],
    "messageBroker": false,
    "nativeLanguage": "en",
    "packageFolder": "io/github/jhipster/app",
    "packageName": "io.github.jhipster.app",
    "prodDatabaseType": "postgresql",
    "rememberMeKey": "448f9a67a8a292c4905a733ec22cc3b78e493c56",
    "searchEngine": false,
    "serverPort": "8080",
    "serviceDiscoveryType": false,
    "testFrameworks": ["gatling", "cypress"],
    "useSass": false,
    "websocket": false
  }
}
</pre>
</details>


##### **Environment and Tools**

openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Ubuntu-122.04)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Ubuntu-122.04, mixed mode, sharing)

git version 2.34.1

node: v20.10.0
npm: 10.2.3

Docker version 24.0.6, build ed223bc

##### **JDL for the Entity configuration(s) `entityName.json` files generated in the `.jhipster` directory**

<details>
<summary>JDL entity definitions</summary>

<pre>

</pre>
</details>


Congratulations, JHipster execution is complete!
If you find JHipster useful consider sponsoring the project https://www.jhipster.tech/sponsors/

Thanks for using JHipster!

[mshima]

We should make sure to remove blueprint support for security reason.
Blueprint auto install can install an arbitrary package and execute it.

[mshima]

I will work on disable blueprint support before merging.

[mshima]

Need to fix prettier.

[SudharakaP]

Need to fix prettier.

Thanks. I've fixed prettier as well as added the disable-blueprints flag. 👍🏽

[SudharakaP]

@mshima : Thanks a lot for all the reviews and feedback. 🤗