Resolve "Bash script to download license-db"

What does this MR do?

Adds a script that fetches the license-db export files in chunks of 1000 licenses in a file.

Related issues

Relates to #415848 (closed)

Results of the script

Result Example

v2/apk/1700646799/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1700646799%2F000000000.ndjson?generation=1700646803140154&alt=media
v2/apk/1700646799/000000001.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1700646799%2F000000001.ndjson?generation=1700646804785088&alt=media
v2/apk/1700726497/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1700726497%2F000000000.ndjson?generation=1700726504938369&alt=media
v2/apk/1700812900/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1700812900%2F000000000.ndjson?generation=1700812903424442&alt=media
v2/apk/1700899288/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1700899288%2F000000000.ndjson?generation=1700899291780135&alt=media
v2/apk/1700985688/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1700985688%2F000000000.ndjson?generation=1700985691616288&alt=media
v2/apk/1701072107/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701072107%2F000000000.ndjson?generation=1701072110453092&alt=media
v2/apk/1701158508/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701158508%2F000000000.ndjson?generation=1701158516202830&alt=media
v2/apk/1701244895/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701244895%2F000000000.ndjson?generation=1701244897555181&alt=media
v2/apk/1701331296/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701331296%2F000000000.ndjson?generation=1701331299813099&alt=media
v2/apk/1701421302/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701421302%2F000000000.ndjson?generation=1701421306255832&alt=media
v2/apk/1701507708/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701507708%2F000000000.ndjson?generation=1701507712008579&alt=media
v2/apk/1701594088/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701594088%2F000000000.ndjson?generation=1701594092038495&alt=media
v2/apk/1701680488/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701680488%2F000000000.ndjson?generation=1701680491956508&alt=media
v2/apk/1701766876/000000000.ndjson	https://storage.googleapis.com/download/storage/v1/b/prod-export-advisory-bucket-1a6c642fc4de57d4/o/v2%2Fapk%2F1701766876%2F000000000.ndjson?generation=1701766880207416&alt=media

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product tier badge under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.