Merge from upstream main

[toannhu96]

Summary by Sourcery

Update the Makefile to introduce a new build target with additional linker flags for configuration URL management. Refactor the config package to expose the default configuration URL for external access. Add a new funding information file.

New Features:

• Introduce a new build target 'build-op' in the Makefile to include additional linker flags for the default configuration URL.

Enhancements:

• Refactor the Makefile to use a separate variable for additional linker flags related to the default configuration URL.
• Change the visibility of the 'defaultConfigUrl' variable to 'DefaultConfigUrl' in the config package to allow external access.

Build:

• Add a new configuration URL variable in the Makefile and update build commands to use this variable.

Chores:

• Add a new 'funding.json' file with project funding information.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces changes to the build process, configuration management, and project metadata. It modifies the Makefile to include new build targets and configuration options, updates the config handling in the Go code, and adds a new funding file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Modify Makefile to include new build targets and configuration options	Add CONFIG_URL variable for default configuration URL Update GOLDFLAGS variable to include new configuration URL Add new build target 'build-op' with additional flags Modify existing 'build' target to use CGO_ENABLED=0 Add commented-out build targets for Windows and Mac	Makefile
Update configuration handling in Go code	Change defaultConfigUrl to DefaultConfigUrl (now exported) Update LoadDefault function to use the new DefaultConfigUrl variable	config/config.go
Add new funding information	Create new file with opRetro project ID	funding.json
Minor README update	Remove newline at end of file	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @toannhu96 - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider either implementing the commented-out build targets for Windows and Mac in the Makefile or removing them entirely to keep the file clean and maintainable.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}