fix failing tests after macro msg change

[ash2shukla]

Resolves #

Problem

The message was revised in this PR but the corresponding test assertions were not changed in dbt-core.

Solution

Change the assertion messages to new message.

Checklist

• I have read the contributing guide and understand what's expected of me.
• I have run this code in development, and it appears to resolve the stated issue.
• This PR includes tests, or tests are not required or relevant for this PR.
• This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
• This PR includes type annotations for new and modified functions.

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[tauhid621]

Looks good. Not sure if the dependencies should be modified for the message.

[tauhid621]

Should we also update the exception here

dbt-core/core/dbt/exceptions.py

Line 498 in d3cb077

class DuplicateMacroNameError(CompilationError):

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.33%. Comparing base (d3cb077) to head (557f140).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12506      +/-   ##
==========================================
- Coverage   91.38%   91.33%   -0.06%     
==========================================
  Files         203      203              
  Lines       25455    25455              
==========================================
- Hits        23263    23250      -13     
- Misses       2192     2205      +13     

Flag	Coverage Δ
integration	88.12% <ø> (-0.12%)	⬇️
unit	65.10% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Unit Tests	65.10% <ø> (ø)
Integration Tests	88.12% <ø> (-0.12%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ash2shukla]

Should we also update the exception here

dbt-core/core/dbt/exceptions.py

Line 498 in d3cb077

class DuplicateMacroNameError(CompilationError):

@tauhid621 The exception message was changed for DuplicateMacroInPackageError this is raised in parse time. L498 as per my understanding is compile time so they are independent. If we want to change the message it should be in a separate PR.