Remove unused argument from generate_info_json.sh script call
## Description
> [!TIP]
> _Add a TL;DR when the description is longer than 500 words or
extremely technical (helps the content, marketing, and DevRel team)._
>
> _Please also include relevant motivation and context. List any
dependencies that are required for this change. Add links to Notion,
Figma or any other documents that might be relevant to the PR._
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags=""
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!CAUTION]
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
## Description
PR to add version field in generate info json script. This will be used
to override the version coming from the GH so that hotfixed tags should
refelect the correct version instead of some random commit sha.
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags=""
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!CAUTION]
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No
## Description
PR to add support for custom pg image during the ad-hoc-builder script.
Procedure for the hotfixes from v1.45 is as follows:
### Steps to perform the hotfix:
1. Create a hotfix branch from the tag where we need the hotfix,
`hotfix/<version>` and note down the commit-sha
2. Create hotfix branch `pg-hotfix/<version>` from commit sha on `pg`
branch from step 1
3. Cherry-pick commits from release to hotfix branches
4. Build the server locally by running `./build.sh -DskipTests` within
server directory to avoid any build failures at later stages on both the
hotfix branches
5. If we are seeing any build failure involve `@db-infra` team as
required
6. Run the ad-hoc image builder with `pg-hotfix/<version>` branch to
generate `pg` specific tag `pg-vx.y.z`
7. Do the sanity testing with postgres url
8. Only after successful generation of `pg-vx.y.z` tag from step 4, run
the ad-hoc image builder with `hotfix/<version>` branch to generate
specific tag `vx.y.z` and pass the `pg_tag` created in step 4 i.e.
`pg-vx.y.z`
9. Do the sanity test for mongo DB URLs on `vx.y.z`
10. Ask devops to create latest tags from `vx.y.z` as this is not
supported in the ad-hoc image generation script. Make sure to have
support for platforms: `linux/arm64,linux/amd64`
Fixes https://github.com/appsmithorg/appsmith/issues/36838
/test Sanity
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!WARNING]
> Tests have not run on the HEAD
9af256c80cf2c44b855bb0ea3c009f499bb7b0fc yet
> <hr>Wed, 16 Oct 2024 13:05:17 UTC
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No
## Description
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!CAUTION]
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Chores**
- Updated the workflow for the Ad-hoc Docker Image to include a new step
for preparing server artifacts, enhancing the packaging process.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
