Feat: add no-interactive flag for upgrade.php

[Q4kK]

Having a no-interactive flag is useful because attempting to automate snipe-it upgrades is currently very janky. You have to either:
a) read the prompts and pass in the input (the "correct" way)
a) pipe in input, e.g. yes and hope no new prompts are added.

With a no-interactive flag, this can be fixed by both allowing new prompts to be added without conflict
to user prompts, but also allowing automated upgrades (you could choose to crash, or assign defaults).

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context, providing screenshots where practical. List any dependencies that are required for this change.

Feature addition to upgrade.php, no issue found that could be relevant in fixing.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Run upgrade.php and upgrade.php --no-interactive on any SnipeIT supported php version. --no-interactive runs the upgrade without needing the confirmation prompt.

Test Configuration:

• PHP version: 8.1
• MySQL version: 15.1
• Webserver version: 6.3.4
• OS version: Debian 11

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[welcome]

💖 Thanks for this pull request! 💖

We use semantic commit messages to streamline the release process and easily generate changelogs between versions. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix if it doesn't have one already.

Examples of commit messages with semantic prefixes:

• Fixed #<issue number>: don't overwrite prevent_default if default wasn't prevented
• Added #<issue number>: add checkout functionality to assets
• Improved Asset Checkout: use new notification method for checkout

Things that will help get your PR across the finish line:

• Document any user-facing changes you've made.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[what-the-diff]

PR Summary

• Introduction of a New Variable $no_interactive
  A new variable $no_interactive has been included in the codebase. This variable enables or disables the interactive prompts based on its state.

• Conditional Logic for Interactive Prompts
  The code now contains a condition that checks the status of the $no_interactive variable. Should this variable hold a true value, the software will bypass interactive user prompts, aiding in smoother, uninterrupted workflows.

[snipe]

Hey there - can you retarget this to develop, per our developer documentation?

[Q4kK]

Apologies, should be on develop now.

[welcome]

Congrats on merging your first pull request! 🎉🎉🎉

[kurthuber-dev]

@Q4kK

Hello, I would like to use this feature to automate my SnipeIT updates, but unfortunately the argument does not work properly for me
I get the following message

Am I doing something wrong?

[snipe]

@kurthuber-dev did you try doing a git pull first? It's possible the version of Snipe-IT you have doesn't yet support this, so you might need to pull the latest and then retry the --no-interactive flag.

[kurthuber-dev]

@kurthuber-dev did you try doing a git pull first? It's possible the version of Snipe-IT you have doesn't yet support this, so you might need to pull the latest and then retry the --no-interactive flag.

now it works, thanks a lot