User can add a new skill to their profile

[utunga]

Acceptance criteria

• [ ] There's a way to get to 'edit profile' or 'edit skills' (somehow)
• [ ] You can click to add a new skill
• [ ] When setting the skill you can choose from a list of skills in a drop-down (literally just hardcoded in JSON for now)
• [ ] User can optionally set the hourly rate
• [ ] User can mark themselves as 'available' (and later mark themselves as not available)
• [ ] User can delete a 'skill' from their profile completely (somehow)
• [ ] At some point the user hits 'save' and a bunch of 'availability message' s are published to their ssb feed

[utunga]

This is not a complete design at all but maybe it looks a bit like this

[utunga]

We were thinking about the underlying schema and had these ideas...

This schema is 'folksonomy' capable. So we sould use something like this now but we'll probably jsut hard code the lsit of skills for now.

IRawSkillMessage
- Skill : String

AvailabilityMessage : IRawSkillMessage
- Skill : String
- Available : Bool
- HourlyRate : Number?
- CurrencyCode : String?

RequestMessage : IRawSkillMessage
- Skill : String
- ...etc ..

An even more sophisticated schema would let a commuity admin have a role in somehow editing the list of available skills and adding icons for them etc

AvailabilityMessage : Message
- Skill : RawSkill
- Available : Bool
- Hourly Rate : Number

* usually published by a community admin

RawSkill
- Text : String
- SuggestedSkillMessageID : MessageID 

SuggestedSkillMessage : Message
- Text : String
- Icon : ImageUrl
- Aliases : String[]

CommunitySkill : Skill
- Id
- Icon 

SkillId : Int

SkillMessage : Message
- Text
- Icon (?)

[luandro]

• [x] Create update profile page / routes
• [x] Link from profile page
• [ ] Add ui for showing and adding new skills
• [ ] Create ssb-crut for availability and skills
• [ ] Create graphql schema and resolvers
• [ ] Connect api and ui