Declaring a function as a friend within a class gives that function the ability to access the class's private and protected members. However, it doesn't make that function a member of the class. A friend function remains a non-member function, but it's just granted special access privileges.

To determine if a year is a leap year, we need to check if the year is divisible by certain numbers. The modulus operator (%) gives the remainder of a division and can be used to check for divisibility. The equality operator (==) is used to check if the remainder is zero. Hence, the combination of % and == is crucial to check the divisibility conditions required to determine a leap year.

In tail recursion, the function's recursive call is the last action executed. The significance of tail recursion is that the current function frame can be discarded before the recursive call is made, potentially allowing compilers to optimize the recursion by reusing the current function's stack frame for the next.

A stack overflow error typically indicates that there's too much recursion, causing the system's stack to exceed its capacity. One effective way to resolve this is by converting the recursive algorithm to an iterative process using loops, which can help manage the stack better and prevent such errors. This retains the logic without heavily depending on the system's stack.

In C++, when multiple 'if' conditions are true, only the block corresponding to the first true condition will be executed. Subsequent true conditions are ignored.

The break statement is primarily used for exiting a loop or a switch when a specific condition is met. In a professional codebase, it's particularly useful for scenarios where processing should not continue once a certain condition has been satisfied, ensuring efficient and intended behavior.

Using feature branches and regularly merging them into the main branch helps detect and resolve conflicts early. It ensures that the main branch remains stable, as conflicts are addressed incrementally. Options 1, 3, and 4 suggest approaches that are not recommended for maintaining a stable main branch in a collaborative environment.

Git rebase rewrites commit history, which can lead to conflicts for collaborators who have already pulled the changes. It's important to use it carefully in a shared repository to avoid disrupting others' work.

The 'pre-receive' hook is invoked before any references are updated, allowing rejection of updates. In contrast, 'post-receive' is invoked after all refs have been updated, making it useful for triggering actions after the update. Understanding their timing is crucial for implementing custom Git workflows.

In a complex project, a "Pre-commit" Git hook can be set up to enforce commit message standards before the actual commit is made. This ensures consistency in commit messages and helps maintain a clean commit history.