Namespaces: Renamings

[MImmesberger]

What problem do you want to solve?

This PR provides the necessary renamings of taxes and transfers functions for #804.

[MImmesberger]

I have finished renaming all taxes. (I will postpone transforming the qualified names in the tests to a tree structure until the very last step, it's hard to make changes after that.)

@hmgaudecker a style question: Do you have an opinion about how we handle cases where the qualified names are longer than 88 characters?

In the sozialversicherungsbeitraege/pflegeversicherung/__init__.py module we have:

@policy_info(
    start_date="1995-01-01",
    end_date="2004-12-31",
    name_in_dag="betrag_selbständig_m",
)
def betrag_selbständig_ohne_zusatz_fuer_kinderlose_m(
    sozialversicherungsbeitraege__krankenversicherung__einkommen__bemessungsgrundlage_selbständig_m: float,
    sozialversicherungsbeitraege__pflegeversicherung__beitragssatz__betrag: float,
) -> float:
    """Self-employed individuals' long-term care insurance contribution until 2004.

I'd say its better to make an exception to the rule here than to remove nesting levels or use abbreviations. Do you agree?

[hmgaudecker]

Scary! But yes, most definitely agree! Just append a # noqa... to that line.