In the OpenStreetMap data schema that's called 'tags'. Postgresql calls it 'hstore'. I've seen 'tuple' and 'set' used but overall it's easier for the reader to stick to key-value or name-value I think.
Some languages use "dictionary".
Details
Dictionary
Tags.
Named value?
Details?
Building is easy, naming is hard. In this case though, you're overthinking it. Pick one and move forward. Attributes is super common to use in these scenarios. Properties is also common and wouldn't be out of place.
I like to always build a project dictionary early on, as it just is helpful for everyone coming along later, and also if concepts change over time the original intent is clear. So like in this case, I'd just pick "attributes" and then have a markdown file or wiki etc that has common terms, and attributes would be described with examples. A quick 1-2 sentence write up is way easier then trying to spend a lot of time picking the perfect word/phrase.