Please verify that this bug has NOT been raised before.

• I checked and didn't find a similar issue

Describe the bug*

There's no "order stock" button against Build order line items that are tracked parts:

I can see why the "allocate stock" button is not usable here, but is there any reason there can't be an "order stock"?

Steps to Reproduce

1. Add a BOM to a part with a tracked component part
2. create a build order for the parent part
3. observe the build order line items page

Expected behaviour

Be able to order stock like with non-tracked parts

Deployment Method

• Docker
• Package
• Bare metal
• Other - added info in Steps to Reproduce

Version Information

Version Information:

InvenTree-Version: 0.17.0 dev
Django Version: 4.2.16
Commit Hash: 6bf6733
Commit Date: 2024-11-18

Database: sqlite3
Debug-Mode: False
Deployed using Docker: True
Platform: Linux-6.6.50-x86_64-with
Installer: DOC

Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.1.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}, {'name': 'InvenTreeCurrencyExchange', 'slug': 'inventreecurrencyexchange', 'version': '1.0.0'}, {'name': 'InvenTreeLabel', 'slug': 'inventreelabel', 'version': '1.1.0'}, {'name': 'InvenTreeLabelMachine', 'slug': 'inventreelabelmachine', 'version': '1.0.0'}, {'name': 'InvenTreeLabelSheet', 'slug': 'inventreelabelsheet', 'version': '1.0.0'}, {'name': 'DigiKeyPlugin', 'slug': 'digikeyplugin', 'version': '1.0.0'}, {'name': 'LCSCPlugin', 'slug': 'lcscplugin', 'version': '1.0.0'}, {'name': 'MouserPlugin', 'slug': 'mouserplugin', 'version': '1.0.0'}, {'name': 'TMEPlugin', 'slug': 'tmeplugin', 'version': '1.0.0'}, {'name': 'Autolinker', 'slug': 'autolinker', 'version': None}, {'name': 'Farnell Plugin', 'slug': 'farnell-plugin', 'version': '1.0.0'}, {'name': 'RS Barcode Plugin', 'slug': 'rs-barcode-plugin', 'version': '1.0.0'}, {'name': 'Partnabber', 'slug': 'partnabber', 'version': '0.0.0'}]

Please verify if you can reproduce this bug on the demo site.

• I can reproduce this bug on the demo site.

Relevant log output