Added Purchase Cost to Asset Model

[Godmartinz]

Description

This adds a purchase_cost to the models table. If an asset assigned the model leaves a blank purchase cost when creating a new asset, it will inherit the purchase cost from the model This only applies to when creating assets, and will not happen when updating or leaving the purchase cost blank in an edit
A help info line has been added to the create route.

On the create route:

On the Update/edit route:

Fixes #15237

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• [ x] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

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

• Test A
• Test B

Test Configuration:

• PHP version:
• MySQL version
• Webserver version
• OS version

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

[what-the-diff]

PR Summary

• Introduction of Purchase Cost Field
  The code introduces a new field named purchase_cost. This means that both our asset models and individual assets will now have an additional piece of information related to their buying prices.

• New Purchase Cost Calculation Method
  A new method named purchaseCostExplicit has been added to our assets. This new method will help us in calculating the explicit purchase cost more efficiently.

• Database Update
  The database schemas for our model and asset tables have been updated to accommodate this new purchase_cost attribute. This is done by a newly added migration file.

• New Cost Info View
  A new blade view file named purchase_cost.blade.php has been added to provide a dedicated view for this new purchase cost information. This will make it easier for users to view this information.

• Modification for Existing View
  Additionally, a minor change has been made to the existing 'models' view file (edit.blade.php). This is done to incorporate the new purchase_cost field and provide a smoother user experience.

[snipe]

I'm not sure we want to do an explicit thing here. I think (similar to the way eol date used to work) we just offer that as a prepopulated value when the asset gets created.

[Godmartinz]

Question: if there was purchase of a model with upgrades making it a different cost then the model, do we want to put an indicatior for some reason on the asset info page noting that?

[snipe]

Question: if there was purchase of a model with upgrades making it a different cost then the model, do we want to put an indicator for some reason on the asset info page noting that?

Perhaps just noting the model's default price would be enough? That could get confusing if the model's cost went up over time though - could make it look like it's a cheaper machine, when really it's just an older machine.

[snipe]

The challenge I see here is that if someone wants to deliberately leave a purchase cost blank on an asset, there isn't really a way to do it using this method.

[snipe]

Ping @Godmartinz

[Godmartinz]

Should we maybe add a button next to the input Use Asset Model price that would populate the price? @snipe
We would avoid oversight and the need to search for the price that way.