[Projects] Fix BC for GET requests of non-normalized function names

[yaelgen]

follow up for: #3287
In this previous PR we added a normalization to a function name before saving it, and notify the user of the change.

We realized that in case our users ignored/missed the warning when setting the function, and then attempted to access (import or update) it later, they would be unable to do so using the old name, and would not know why their function was not found.

As a result, as long as we do not block requests with non-normalized names, we will normalize GET requests as well.
In this fix we handle this case by adding fall-back to get_function:
Normalize the requested name and attempt to retrieve it from the database. if no response is received, we will check to see if the original name contained underscores, if so, we will repeat the retrieval and return the result (if exists).

The backwards compatibility behavior here is:
In circumstances when the user has an old function with non-normalized name already saved in the database, he will be able to retrieve it.
If he makes an update request, we will create a new updated function, with a normalized name. Now if he attempts to retrieve it using the old name, we will first normalize the name in the request for him, and return the updated function.

[Tankilevitch]

Nice Job! very concise and straight to the point @yaelgen

[liranbg]

Well done! few things

1. Add type hint / param explanation for public functions you encounter and change, will help future developers
2. Public functions before private functions, try to push down the internal implementation of get function after all public class apis
3. It is legitimate to log that you function was not found, trying to find function without normalizing its name

[liranbg]

last one

[Tankilevitch]

LGTM

[Tankilevitch]

LGTM