[Improvement]: Improvements to `bal deprecate` command

[Shammi Kolonne]

Description

There are two noticed improvements that can be done.

1. When a package is deprecated, this is identified by a deprecated.txt msg that resides within the relevant package bala. When a user package uses the deprecated dependency under the conditions

   • The user package was last build within 24 hours or user continues to build the package with the --sticky flag
   • The dependency package was deprecated in central during this time.
     the bala in the user's local cache won't be updated with the new deprecated information. Hence the user will continue to be in the dark regarding the recent deprecation.
     We can improve this to update the local bala when a bala is deprecated in central.

2. If a message is not provided when executing bal deprecate, the deprecated warning will show the reason for deprecation as null

WARNING [jwttest2] shammi/jwttest:1.1.0 is deprecated: null

We can improve this to not show anything when the message is null

Describe your problem(s)

No response

Describe your solution(s)

No response

Related area

-> Other Area

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response