Fixes the examples for the attribute_generation micro_service

In the example the ordering of target_provider and requester was the
reverse from what is used in the code.

Author: skanct

example/plugins/microservices/attribute_generation.yaml.example

@@ -2,8 +2,8 @@ module: satosa.micro_services.attribute_generation.AddSyntheticAttributes
 name: AddSyntheticAttributes
 config:
     synthetic_attributes:
-        target_provider1:
-            requester1:
+        requester1:
+            target_provider1:
                 eduPersonAffiliation: member;employee
         default:
             default:

src/satosa/micro_services/attribute_generation.py

@@ -61,8 +61,8 @@ class AddSyntheticAttributes(ResponseMicroService):
 name: AddSyntheticAttributes
 config:
     synthetic_attributes:
-        target_provider1:
-            requester1:
+        requester1:
+            target_provider1:
                 eduPersonAffiliation: member;employee
         default:
             default:
@@ -72,8 +72,8 @@ class AddSyntheticAttributes(ResponseMicroService):
 ```
 
 The use of "" and 'default' is synonymous. Attribute rules are not
-overloaded or inherited. For instance a response from "target_provider1"
-and requester1 in the above config will generate a (static) attribute
+overloaded or inherited. For instance a response for "requester1"
+from target_provider1 in the above config will generate a (static) attribute
 set of 'member' and 'employee' for the eduPersonAffiliation attribute
 and nothing else. Note that synthetic attributes override existing
 attributes if present.