Allow editing of asset number

[CarlosNZ]

Fixes #5392

👩🏻‍💻 What does this PR do?

This is the simplest version of this -- it just makes the Asset number editable after the asset is created. I'll make a follow-up issue to get user input on scanning, as that's a bit more involved and could do with some further planning to make it work nicely.

💌 Any notes for the reviewer?

I notice we're not enforcing unique-ness for Asset number. Should it be?

🧪 Testing

• Go to an Asset detail page
• Can edit the Asset Number
• Can save, and Asset number is updated in the Breadcrumb title at the top of the page

[CarlosNZ]

Follow-up: #5652

[github-actions]

Bundle size difference

Comparing this PR to main

Old size	New size	Diff
4.99 MB	4.99 MB	186 B (0.00%)

[adamdewey]

I notice we're not enforcing unique-ness for Asset number. Should it be?

It would be nice, but not sure how we would do it if assets can be added offline?

[jmbrunskill]

We an asset number duplication check in the insert method.
Now that we're updateing it from upsert it should be there too

    if let Some(asset_number) = &input.asset_number {
        if check_asset_number_exists(asset_number, connection)?.len() >= 1 {
            return Err(InsertAssetError::AssetNumberAlreadyExists);
        }
    }

Can you add this to the validate method in the update please?

I agree @adamdewey we can't guarentee it doesn't get duplicated with sync but would be good to keep it unique for a site at least.

[jmbrunskill]

Approved, but can you add that duplication check, or put a follow up issue for that to be picked up refactor week?

[jmbrunskill]

Can you add this to the validate method in the update please?

On second thoughts I think we'll need to make it check that it's not the same id that the current asset is using.
I think a follow up issue is fine...