feat: add profile labels to machine profile type

[benfurber]

PR Checklist

• - Commit messages are descriptive, it will be used in our Release Notes
• - Unit and e2e tests for the changes that have been added (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Feature (adds functionality)
• Code style update
• Refactoring (no functional changes)
• Build related changes
• CI related changes
• Documentation changes
• Other... Please describe:

What is the current behavior?

Currently the profile type machine shop has a custom profile attribute.

What is the new behavior?

This removes that custom attribute and replaces it with a more generic field that all profile types will eventually use.

https://www.figma.com/design/x4DcaUjwiigjCySAt5omxB/CP-%2F-Signup%2C-Settings-and-Gatekeeping?node-id=1140-2633&node-type=frame&t=MryI3JVwVnwhTJMn-11

Part of #3908

[benfurber]

@mariojsnunes I'm starting to work on this

Ideally the labels are DB stored/content editable for mods. But I'd rather that done later down the line. Do you think this service pattern is appropriate for this usecase? These labels will end up being called at least on the map, profiles and settings.

[cypress]

onearmy-community-platform    Run #6392

Run Properties:   Passed #6392  •  2a2be7452d: feat: update architectural design

Project	onearmy-community-platform
Branch Review	pull/3904
Run status	Passed #6392
Run duration	17m 01s
Commit	2a2be7452d: feat: update architectural design
Committer	Ben Furber
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	5
Pending	0
Skipped	0
Passing	78
View all changes introduced in this branch ↗︎

[davehakkens]

Are you making them profile-type specific @benfurber? -as they should work cross all profile-types

[benfurber]

Are you making them profile-type specific @benfurber? -as they should work cross all profile-types

@davehakkens Generic is the direction of travel.

[mariojsnunes]

@mariojsnunes I'm starting to work on this

Ideally the labels are DB stored/content editable for mods. But I'd rather that done later down the line. Do you think this service pattern is appropriate for this usecase? These labels will end up being called at least on the map, profiles and settings.

Looks good! It can easily evolve into calling an API

[davehakkens]

What is the end state of the travel you have in mind @benfurber? -so I understand better how to 'review' this

[benfurber]

@davehakkens The to-do list for this work

[davehakkens]

Nice thanks for the update. Sounds good to me

[benfurber]

Update. Worked with Mario on this for a bit. We got caught on a build error. Going to change the tech approach on this. Will resume work on it Monday.

[benfurber]

(All the hard work is in this branch, most of the rest should be straightforward after this.)

[benfurber]

Right. I think is is finally ready now. So will work on the PP database change tomorrow.

[benfurber]

Data updated and looking good. Deploying this now.

[onearmy-bot]

🎉 This PR is included in version 2.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀